894M1 UBE on As400 Eserver Error Out

[coolworm]

Hi,
Want to find out if anyone has the same encounter.
I put dowm 894_M1 in my 8.11 environment. Enterprise server is an As400 running V5R3 with all the latest PTTs installed.
Strange thing is after 894_M1 has been installed and E1 services came up, I was able to submit a UBE report on the As400 for the first time but subsequent submission of ANY UBE report on the As400 will not run and error out.
See below for the server jde.log.

---------------
2931 Fri Aug 19 18:33:00.978232 dbdrv_log.c196
OS400QL009 - OpenSQLCursor:Open SQL cursor: Crsr16. QSQLMSG *LIBL - SQL7008 - &1 in &2 not valid for operation

2931 Fri Aug 19 18:33:00.988336 dbdrv_log.c196
OS400CC004 - StartJournalFile:Command STRJRNPF FILE(SVM811/F986111 ) JRN(OWJRNL/OW_JRNL ) IMAGES(*BOTH) OMTJRNE(*OPNCLO). Failed with exception CPF9822

2931 Fri Aug 19 18:33:00.988696 jdb_drvm.c971
JDB9900401 - Failed to execute db request

2931 Fri Aug 19 18:33:00.989024 jdb_utl1.c2936
JDB9900355 - Failed to Select from F986111

2931 Fri Aug 19 18:33:01.271112 dbdrv_log.c196
OS400QL009 - OpenSQLCursor:Open SQL cursor: Crsr16. QSQLMSG *LIBL - SQL7008 - &1 in &2 not valid for operation

2931 Fri Aug 19 18:33:01.280184 dbdrv_log.c196
OS400CC004 - StartJournalFile:Command STRJRNPF FILE(SVM811/F986111 ) JRN(OWJRNL/OW_JRNL ) IMAGES(*BOTH) OMTJRNE(*OPNCLO). Failed with exception CPF9822

2931 Fri Aug 19 18:33:01.280544 jdb_drvm.c971
JDB9900401 - Failed to execute db request

2931 Fri Aug 19 18:33:01.280872 jdb_utl1.c2936
JDB9900355 - Failed to Select from F986111

2931 Fri Aug 19 18:33:01.938040 dbdrv_log.c196
OS400QL016 - ExecuteSQLRequest: QSQLMSG *LIBL - SQL0803 - Duplicate key value specified

2931 Fri Aug 19 18:33:01.938400 jdb_drvm.c971
JDB9900401 - Failed to execute db request

2931 Fri Aug 19 18:33:01.938840 jdb_exet.c5454
JDB3400009 - Failed to perform Insert for F986110

2931 Fri Aug 19 18:33:01.939184 jdeknube.c1125
KNT0000086 - JDB_InsertTable failed for F986110
-----------------------------

I have gone back to Peoplesoft about this but so far they have no clue.

Any help will be appreciated. Thanks in advance.

CW
As400, v5r3, 8.11, 894_M1

 

[DRezanka]

We are having a similar problem with the STRJRNPF with our Media Object Attachments that is stumping ORAPSFTJDE. Let us know if you find a solution to your issue.

In our case, we have two OWJRNL's (one for Xe) and we are wondering if the developer hardcoded a reference to OWJRNL instead of using the Data Source.

 

[ball123]

The SQL7008 error is a result of the file not being journaled. It looks like it is trying to start the journaling for you, but is getting a file authority error (CPF9822). You might want to check that the profile this is running under has the proper authority to the file or start the journaling on the file yourself.

 

[coolworm]

The thing is when my 8.11 env. is on 894_D1, UBEs can be submiitted on the As400 with no problem at all but when I upgraded to 8.94_M1, UBEs cannot be submitted anymore.
Wonder what Peoplesoft did to the 894_M1 code.

CW

 

[cdawes]

When you change service packs this is often an issue.

When you stop JDE the journaling is likely still running. You can start journaling on individual files by running the following command:

STRJRNPF FILE(PRODDTA/F0101) JRN(OWJRNL/OW_JRNL)

To start Journalling on ALL JDEDWARDS files run the following:

OWJRNL\INSTALLSP

You can avoid this issue by stopping journalling EVERYTIME you stop JDEdwards (but then again I've never done that).

 

[pshook]

Did you ever find a solution for this? We are having a similar problem.

 

[Dmitry]

If you have the same error:
STRJRNPF FILE(SVM811/F986111 ) JRN(OWJRNL/OW_JRNL ) IMAGES(*BOTH) OMTJRNE(*OPNCLO). Failed with exception CPF9822

Try to run this command in AS400, you will see the error with file authority.

So this is true: "The SQL7008 error is a result of the file not being journaled. It looks like it is trying to start the journaling for you, but is getting a file authority error (CPF9822). You might want to check that the profile this is running under has the proper authority to the file or start the journaling on the file yourself."

I had the same with SVM811 library. So the fix is next:
OS Admin provided next permissions to this library:
PUBLIC - *ALL
PSFT - *ALL
ONEWORLD - *ALL
and error is gone.