Import (Tbl Load) without LOG -> Tbls read-only (error: -115 and -126)

[Former Member]

Hi everybody,

I'm very new to this things, so I'am sorry for mistakes, but I see no other way, then bothering you with what makes me crazy, so I startet in distributing this help scream a little bit more than perhaps needed.

But I have a problem with my SAP DB 7.4 on Windows 2000 SP4, setting the permissions of tables, I loaded with the loadercli, what I cant't solve.

The data is okay, the application runs (as long as nobody is trying to update, delete or insert data), but I can`t find any option to set the permissions of the tables, neither in the DB Manager nor in the SQL Studio.

For better understanding what I have done:

I exported the 7.4 DB with the 7.6 loader from a desktop computer and imported it into my server-DB. The 7.4 loader was not able to do this, so I tricked it out the hard way by substituting it with the one packed to the newest MaxDB version.

Now everything is read-only, because I forgot (or more precise: I didn't expect this to be that really BIG problem) to export and import the LOG.

The desktop DB was cleared/killed/deleted after my application runs on the server. (I idiot didn't test to update/delete or insert data)

I gathered a lot of information via google and the SAP DB Library, but non helps me.

The Library only says:

-

---

-115: Table is read only

Explanation:

The attempt was made to perform an <INSERT>, <UPDATE> OR <DELETE statement>. But the specified table only allows reading SQL statements because it was previously loaded with the NOLOG option.

User Action:

The read-only mode can be implicitly cancelled saving data or pages using the database administration tool.

-

---

I understand, because I loaded no LOG, that there is no LOG.

And the resulting error of this I understand too, which is called: -126 Databackup missing (Backuphistory lost) (which is not descriped in the library)

But why is it not possible to start from this point, with a new log, and the old data? (that is consistent)

So I perhaps need to know 2 things to solve this (I think):

1. How can I reinitialize/recreate/reconfigure a LOG and the Backuphistory?

2. What do I need to do next to set the permissions back to R/W?

Sorry for that many questions and my unknowing, but I can't help myself anymore and my company must work with their application.

Any suggestions to solve this problem are welcome with high gratification!

Thank all of you taking time of this, in hope that there is anybody who can help me, I really need to get this running again.

Frank

[Former Member · Accepted solution]

Hi Alexander,

unfortunately I didn't do that. I made a complete data backup, but forgot the LOG :(.

I took the commands like them are documented.

(If I remember right these where the commands)

1. loadercli -d <DB> -u <DBU>,<DBUPW>

2. > use user <USER>,<USERPW>

3. > export USER CATALOG OUTSTREAM FILE 'C:\ucat.sql' DATA

OUTSTREAM FILE 'C:\udata.sql'

4. > import ... INSTREAM FILE ...

Thanks for trying to help!

[alexander_schroeder · Accepted solution]

Hello Frank,

I meant: Did you made a complete data backup of the

target database (where now the tables are locked)?

A complete backup of the database will hopefully

remove the 'locked' state.

Regards

Alexander Schröder

[Former Member]

Hi Alexander,

I did a complete Backup with the GUI, and you were fully right, it runs again!!! Thanks a lot for this tip. Till Friday I have had called me a professional programmer, but I feel like a newbie now, with a lot to learn about DB.

If the exists a link to deeper knowlegde about this behavior I will for sure start reading, is there any?

I offer in making an addition to the SAP 7.4 Documentation related to this. When I also know that perhaps nobody except me is using SAPDB 7.4. But again thanks for the help.

Greetings,

a new born db user

[Former Member]

If you mean with the DB Manager, then no.

I tried to set autolog to on and searched for features to set the permissions, played with the command line, all that stuff, but saw no reason to make again a backup. I'll try that, sometimes the way is not logical to get things running, but if it helps I'll do nearly anything.

Except writing my own export and import tool for that reason 😕

I don't can test this today anymore, the last 3 days where enough, so I'll do it on monday, but have thanks so far, for this suggestion.

Frank

[alexander_schroeder]

<deleted>

Message was edited by: Alexander Schroeder

[Former Member]

wrong forum - deleted

Message was edited by: Peter Simon

[alexander_schroeder]

Hello Frank,

did you try to make a complete database backup?

Regards

Alexander Schröder