new tables not being journaled

[Former Member]

Hi,

recently, we performed an homogeneous system copy from our ECC productive system to the QAS.

We followed the procedure as usual and everything seems to work fine except whenever we create a new table on DEV and transport it to QAS, the SAP system generates the following error messages:

On SM21:

Database error 7905 at EXE

Table ZSD_OU in R3Q00DATA created but could not be journaled

MSGID= Job=333598/Q0010/WP32

On ST11, WP32 developer trace:

ds_dbsl_funs.execute returned 102.

SQLCode: -601.

SQLText: ZSD_OU in R3Q00DATA type *FILE already exists. MSGID= Job=333598/Q0010/WP32.

On OS level, the table does not exist nor can be created using SE11 (although it exists on DD)

The procedure I've been following to correct this issue is:

1. create the table directly on the database using SQLUTIL and the CREATE TABLE SQL clause found on the developer trace

2. start journaling the table by issuing the command

STRJRNPF FILE(R3Q00DATA/ZSD_OU) JRN(R3Q00DATA/QSQJRN) IMAGES(BOTH) OMTJRNE(OPNCLO)

3. activate the table on SE11

4. create the index on SE11's database utility menu option

Of course, this is just a workaround and we need to get all new objects being automatically journaled on OS level.

Does anyone know what must be done?

Does a AS4FIXFILE command solve the issue (although it was already issued before I started SAP for the first time after the homogeneous copy)?

Thanks

Antonio

Edited by: António Barrote on Jun 12, 2008 2:49 PM

[dorothea_stein]

Hi Antonio,

AS4FIXFILE will only fix existing tables, but it would not prevent that you keep getting errors for new tables... Something is wrong with your journal. Please check the joblog for messages preceeding the SQL7905.

Please also check WRKJRNA R3sidDATA/QSQJRN. For "Receiver size options" you should see *RMVINTENT and *MAXOPT2.

In case you only see MAXOPT1, you will need to adjust your journal settings.

Best regards,

Dorothea

[Former Member]

thanks for the help..

the problem is now solved

[Former Member]

Hi,

yes, AS4FIXFILE command will solve the issue.

the following is from SAP Note 116192 - AS/400: SQL error -7008

If several (or all) files in the database library are affected, you can also execute the command AS4FIXFILE from the kernel library to start journaling for all files in the database library. Submit AS4FIXFILE with the following command:

SBMJOB CMD(AS4FIXFILE DBLIB(R3<SID>DATA) CHGOWN(*YES)

ENDJRN(YES) STRJRN(YES)) JOB(AS4FIXFILE)

regards,

kaushal