If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Informix > after ontape -N db, i always get 256 SQLCODE

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-05-07, 11:33
meiwen meiwen is offline
Registered User
 
Join Date: Oct 2005
Posts: 30
after ontape -N db, i always get 256 SQLCODE

i use C++ to connect DB.
after using ontape -N db,
there is no problem to create proc, and disable triggers ect.
but when i try to execute the proc,i always get 256 error code?

finderr 256
-256 Transaction not available.

You cannot begin a transaction in this database because it does not
have a transaction log. In order to support transactions, you must
start a transaction log. Refer to your Administrator's Guide for
information on how to start a transaction log.



is it normal error message?
how to avoid it?

thanks in advance.
Reply With Quote
  #2 (permalink)  
Old 09-05-07, 16:42
jwain jwain is offline
Registered User
 
Join Date: Aug 2003
Location: Allentown pa
Posts: 41
Yes ontape -N dbname turns off logging to start a transaction begin work commit etc you need to have loggin set to either Buffered or unbuffered loggin ontape -U or ontape -B
__________________
Jeff Wain
Reply With Quote
  #3 (permalink)  
Old 09-06-07, 03:11
meiwen meiwen is offline
Registered User
 
Join Date: Oct 2005
Posts: 30
ontape -N DB1 -B DB1

if i use command above,

Database 'DB1' - Logging status updated.
Database 'DB1' - Logging status updated.

Program over.


what's that meaning? unbuffer first, then buffer again?

Can I use -N and -B , -U at same time?

what kind of command i can check the DB in exactly which status concern the log?

Thanks in advance.
Reply With Quote
  #4 (permalink)  
Old 09-06-07, 04:48
meiwen meiwen is offline
Registered User
 
Join Date: Oct 2005
Posts: 30
Problem solved, in the procedure, there is begin work, which open transaction, i remove this begin work, it is ok now.
Reply With Quote
  #5 (permalink)  
Old 09-06-07, 15:31
jwain jwain is offline
Registered User
 
Join Date: Aug 2003
Location: Allentown pa
Posts: 41
There ya go when setting the loggin only use one option in the future -U = Unbuffered -N = No Logging (which by the way is unsafe if there is ever a crash) the -B if for buffered logging
__________________
Jeff Wain
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On