Problem with logging.
Posted in 2008
After restoring a dropped database with tbload on an old INFORMIX-OnLine 5.10 system (Linux 2.2), the user hit error 568, "Cannot reference an external database without logging." Respondents explained that cross-database references require matching logging modes; checking tbmonitor (Status > Databases) showed the existing databases were unbuffered logging (U) while the reloaded one had none (N). The fix was to run `tbtape -s -U databasename` (turning logging on must be combined with an archive) and follow the prompts, which worked. Others also warned that TAPEDEV set to /dev/null means no real backup.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: General Discussion
Hi, Sorry about my english... It is not so good, i need help about informix. I have some database, i happen to remove one db. After load database from backup (tbload -l ...) informix show an error 568 Cannot reference an external database without logging. What i do wrong ? Any ideas? -- Pietia
You have reloaded the database with the incorrect logging mode.
Somewhere you have a client that is connecting to multiple databases
through the single session handle, using remote syntax
<database>@<host>:<table>
This only works in the logging mode of the two databases is the same.
Use onmonitor (maybe tbmonitor in your environment - what version and
what platform are you on?) to have a look at the database logging modes.
Then you can use ontape (with TAPEDEV set to /dev/null on UNIX or NUL on
Windows) to alter the logging modes of the databases.
If you can't find the utility, run "SELECT * FROM sysdatabases" from the
sysmaster database - it shows the same thing.
Find which database is incorrect and change it's logging mode to match
the other one used by the client.
Jarrod Teale
Fonterra New Zealand
-----Original Message-----
From: informix-list-bounces@iiug.org
[mailto:informix-list-bounces@iiug.org] On Behalf Of Pietia
Sent: Monday, 10 November 2008 5:11 a.m.
To: informix-list@iiug.org
Subject: Problem with logging.
Hi,
Sorry about my english... It is not so good, i need help about informix.
I have some database, i happen to remove one db. After load database
from backup (tbload -l ...) informix show an error 568 Cannot reference
an external database without logging. What i do wrong ?
Any ideas?
--
Pietia
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
DISCLAIMER:
This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email.
You may not use, disclose or copy this email or its attachments in any way.
Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group.
http://www.fonterra.com/
Jarrod Teale:
> Use onmonitor (maybe tbmonitor in your environment - what version and
> what platform are you on?) to have a look at the database logging modes.
> Then you can use ontape (with TAPEDEV set to /dev/null on UNIX or NUL on
> Windows) to alter the logging modes of the databases.
I have INFORMIX-SQL Version 5.10.UC1 on Linux 2.2.
Can you show me step by step what i must to do?
i have tbmonitor, i set in tbconfig
TAPEDEV /dev/null
what next?
> If you can't find the utility, run "SELECT * FROM sysdatabases" from the
> sysmaster database - it shows the same thing.
i try but database sysmater isnt on my db select list. If i try run
"dbaccess sysmaster" on shell (logged as informix) i have error:
329: Database not found or no system permission. No such file or directory
Thanks for answer.
--
Pietia
First you need to decide what logging mode the database you just loaded
is, and what it should be.
So go into tbmonitor (should be a 4gl style menu system - I haven't
played with version 5.1 in years, hope it's the same)
Select Status then Databases. Scroll down to find the databases you just
loaded. The column Log Status tells you the logging mode the database is
in.
Post the output if you can find it.
>From these, you should see a difference in the logging flags and we can
then work to correct them.
Also, can you confirm that you have tbtape on this system, and that the
options of this command support logging mode changes (look in tbtape -?)
I can't remember for such an old system
Jarrod
-----Original Message-----
From: informix-list-bounces@iiug.org
[mailto:informix-list-bounces@iiug.org] On Behalf Of Pietia
Sent: Monday, 10 November 2008 12:03 p.m.
To: informix-list@iiug.org
Subject: Re: Problem with logging.
Jarrod Teale:
> Use onmonitor (maybe tbmonitor in your environment - what version and
> what platform are you on?) to have a look at the database logging
modes.
> Then you can use ontape (with TAPEDEV set to /dev/null on UNIX or NUL
> on
> Windows) to alter the logging modes of the databases.
I have INFORMIX-SQL Version 5.10.UC1 on Linux 2.2.
Can you show me step by step what i must to do?
i have tbmonitor, i set in tbconfig
TAPEDEV /dev/null
what next?
> If you can't find the utility, run "SELECT * FROM sysdatabases" from
> the sysmaster database - it shows the same thing.
i try but database sysmater isnt on my db select list. If i try run
"dbaccess sysmaster" on shell (logged as informix) i have error:
329: Database not found or no system permission. No such file or directory
Thanks for answer.
--
Pietia
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
DISCLAIMER:
This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email.
You may not use, disclose or copy this email or its attachments in any way.
Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group.
http://www.fonterra.com/
Jarrod Teale pisze: > First you need to decide what logging mode the database you just loaded > is, and what it should be. In tbmonitor my databases have log status U, db loaded from backup have status N. > Also, can you confirm that you have tbtape on this system, and that the > options of this command support logging mode changes (look in tbtape -?) > I can't remember for such an old system I have tbtape: Usage: tbtape { [-s] | [-c] | [-a] | [-r] | [-N database ...] [-U database ...] [-B database ...] } -s Archive all dbspaces/BLOBSpaces. -c Continuous backup of logical logs. -a Automatic backup of logical logs. -r Restore entire INFORMIX-Online sytem. -N Set the following database(s) to no logging. -U Set the following database(s) to unbuffered logging. -B Set the following database(s) to buffered logging. - Turning on logging for a database must be combined with -s option. -- Pietia
DjAvX wrote:
> Jarrod Teale pisze:
>> First you need to decide what logging mode the database you just loaded
>> is, and what it should be.
>
> In tbmonitor my databases have log status U, db loaded from backup have
> status N.
>
>
>> Also, can you confirm that you have tbtape on this system, and that the
>> options of this command support logging mode changes (look in tbtape -?)
>> I can't remember for such an old system
>
> I have tbtape:
>
> Usage: tbtape { [-s] | [-c] | [-a] | [-r] |
> [-N database ...] [-U database ...] [-B database ...] }
>
> -s Archive all dbspaces/BLOBSpaces.
> -c Continuous backup of logical logs.
> -a Automatic backup of logical logs.
> -r Restore entire INFORMIX-Online sytem.
> -N Set the following database(s) to no logging.
> -U Set the following database(s) to unbuffered logging.
> -B Set the following database(s) to buffered logging.
>
> - Turning on logging for a database must be combined with -s option.
>
Well, apart from the fact that YOU DO NOT HAVE A BACKUP :
"i have tbmonitor, i set in tbconfig
TAPEDEV /dev/null"
You should be able to run :
tbtape -s -U databasename
and follow the prompts.
This may have issues with TAPDEDEV set to /dev/null (Version 5.10 is pretty old now, and so is Linux 2.2).
What happens if your disks blow up? Sort out a backup :-/
TBP: > tbtape -s -U databasename > > and follow the prompts. It works! ;) > This may have issues with TAPDEDEV set to /dev/null (Version 5.10 is > pretty old now, and so is Linux 2.2). i know, but this system must work max to 01.01.2009 > What happens if your disks blow up? Sort out a backup :-/ i have backup from dbunload Thanks for your and Jarrod help. -- Best regards Pietia