Direct links to fixes
APAR status
Closed as fixed if next.
Error description
The @SCHEMA@ replacement variable in the cell-level database of an IBM Business Process Manager Advanced environment is missing from the template createSchema_CommonDBCellOnly.sql file for Oracle.
Local fix
When you create the IBM BPM Advanced deployment environment that uses an Oracle database, set bpm.de.deferSchemaCrreation=false and then manually add the missing schema qualifier <userName> to the following CREATE SEQUENCE statements in the generated <profile_root>/dbscripts/<cellName>/Oracle/<databaseName>/<userN ame>/createSchema_Advanced.sql file before creating the database schema: CREATE SEQUENCE SEQ_W_LIT_DOUBLE_ID MINVALUE 1 NOMAXVALUE INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ; CREATE SEQUENCE SEQ_W_LIT_FLOAT_ID MINVALUE 1 NOMAXVALUE INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ; CREATE SEQUENCE SEQ_W_LIT_LONG_ID MINVALUE 1 NOMAXVALUE INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ; CREATE SEQUENCE SEQ_W_NAMESPACE_ID MINVALUE 1 NOMAXVALUE INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ; CREATE SEQUENCE SEQ_W_OBJ_LIT_ANY_ID MINVALUE 1 NOMAXVALUE INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ; CREATE SEQUENCE SEQ_W_OBJ_LIT_DATE_ID MINVALUE 1 NOMAXVALUE INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ; CREATE SEQUENCE SEQ_W_OBJ_LIT_DATETIME_ID MINVALUE 1 NOMAXVALUE INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ; CREATE SEQUENCE SEQ_W_OBJ_LIT_STRING_ID MINVALUE 1 NOMAXVALUE INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ; CREATE SEQUENCE SEQ_W_STATEMENT_ID MINVALUE 1 NOMAXVALUE INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ; CREATE SEQUENCE SEQ_W_URI_ID MINVALUE 1 NOMAXVALUE INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
Problem summary
This issue might occur because the following Oracle SEQUENCE objects are created in the schema of the user who runs the generated createSchema_Advanced.sql script instead of in the schema of the runtime user: SEQ_W_LIT_DOUBLE_ID SEQ_W_LIT_FLOAT_ID SEQ_W_LIT_LONG_ID SEQ_W_NAMESPACE_ID SEQ_W_OBJ_LIT_ANY_ID SEQ_W_OBJ_LIT_DATE_ID SEQ_W_OBJ_LIT_DATETIME_ID SEQ_W_OBJ_LIT_STRING_ID SEQ_W_STATEMENT_ID SEQ_W_URI_ID A fix will be available in IBM BPM V8.5.7 cumulative fix 2017.03 that adds the schema qualifier to the template createSchema_CommonDBCellOnly.sql file for Oracle so the schema qualifier is in the generated SQL files. To determine whether the cumulative fix is available, complete the following steps on Fix Central (http://www.ibm.com/support/fixcentral): 1. On the Select product tab, select WebSphere as the product group, IBM Business Process Manager with your edition from the WebSphere options, All as the installed version, and All as the platform, and then click Continue. 2. In the Text field, enter "cumulative fix", and click Continue. If cumulative fix 2017.03 is available, download and install it. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix.
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
JR57110
Reported component name
BPM STANDARD
Reported component ID
5725C9500
Reported release
855
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-12-02
Closed date
2017-01-25
Last modified date
2017-01-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
04 September 2023