Re: changying from ANSI mode to unbuffered logging
> You need not do a dbexport to change from ANSI mode to unbuffered logging.
Yes you do. According to the Administrator's Guide (v. 7.2, pg 21-3):
Figure 21-1 on page 21-4 shows which database-logging-status transitions
the OnLine administrator can perform and whether they take place
immediately or require a level-0 dbspace backup.
When you add logging (in any form) to a database that formerly did not use
transaction logging, the change is not complete until a level-0 dbspace
backup is performed on all the dbspaces and blobspaces that contain data in
the database. Use the same backup tool (ON-Archive or ontape) to add
logging and create the dbspace backup.
To change the logging status of ANSI-compliant databases, you must unload
and reload the data.
Note specifically the last sentence. The figure 21-1 that they mention shows
that once a database is created in ANSI mode, it can NOT be changed to anything
else.
Mark Collins
mcollins@us.dhl.com
The problem lies in how easily and dangerously we forget that
manipulating things is not the same as understanding them.
> If you are using Informix 5.X then you will have to execute the following
> command.
> Firstly you will have to set the tape parameters as /dev/null.
> After doing so from the $ prompt exectue the following command
> tbtape -s -U <database>
> It will ask you the level of archive to be taken. Specify 0.
>
> If you are using Informix 7.X instead of "tbtape" you will have to mention
> "ontape".
> Below are some other options that can be useful to you..
> -A set the following database(s) to ansi logging
> -B set the following database(s) to buffered logging
> -N set the following database(s) to no logging
> -U set the following database(s) to unbuffered logging
>
> Regards,
>
> Webster
>
>
>
>
> ANTS wrote:
>
> > Yes, that what we are going to do. Recreate the database. If there are any
> > other ways please advise.
> >
> > But, the application developers worried that something might not work if we
> > changed. Any idea?? We have 4GL, stored procedures, and client PowerBuilder
> > applications.
> >
> > Regards,
> >
> > Nien
> > -----Original Message-----
> > From: fernando.collalti@orbit.net <fernando.collalti@orbit.net>
> > To: Sui <Sui>
> > Date: Wednesday, March 11, 1998 11:07 '
> > Subject: Re: changying from ANSI mode to unbuffered logging
> >
> > >
> > >ANTS wrote:
> > >>
> > >> Hi all,
> > >>
> > >> We are planning to change the logging mode from ANSI to unbuffered
> > logging.
> > >> Any consequences that we have to take in 4GL, stored procedures and
> > >> PowerBuilder applications??
> > >>
> > >> Please advise....
> > >>
> > >> Nien
> > >> ===========================================
> > >> Mails are checked daily and processed right away.
> > >> If you don't get my replies within 3 days please send your mail again.
> > >Hello,
> > >
> > >Are you sure that this can be done? Unless you execute a
> > >dbexport and build the database again, it is not possible to change
> > >loggin status from ANSI to unbuffered/buffered.
> > >
> > >
> > >Kind Regards.
> > >
> > >Fernando Collalti
> > >mail: fernando.collalti@orbit.net
> > >
>
>
>
---------------End of Original Message-----------------