Upgr To 188.8.131.52: Looks Like None Of The LSH Jobs(PLSQL, Data Mart) Work Now
Last updated on MARCH 08, 2017
Applies to:Oracle Life Sciences Data Hub - Version 2.4.6 and later
Information in this document applies to any platform.
Recently upgrade to 184.108.40.206 (220.127.116.11 to 18.104.22.168 and then, 22.214.171.124)
Hitting stale connection issue via job and message queue after upgrading to 126.96.36.199, and then, none of the LSH jobs(PLSQL, Data mart) work now
Job Id: 16016195
Submission Type: Submission
Execution status: Submitted
Executable Type: Data Mart Instance
ORA-4061 Existing state of package "APPS.CDR_EXE_RUNTIME" has been invalidated.
Note: The LSH job log and OWB log do have any content in relation to the failed job. Am presuming the job is failing is the submission phase so not getting this far.
SQL> exec mgmt$reorg_sendMsg ('Executing as user: ' || 'CDR_WC81_F4566D');
Executing as user: CDR_WC81_F4566D
SQL> exec mgmt$reorg_checkDBAPrivs ('CDR_WC81_F4566D');
WARNING checking privileges... User Name: CDR_WC81_F4566D
User does not have DBA privs.
The script will fail if it tries to perform operations for which the user lacks
the appropriate privilege.
SQL> exec mgmt$reorg_setupJobTable (44, 'MGMT$REORG_CHECKPOINT', :step_num);
ALTER TABLE "CDR_WC81_F4566D"."T16012941" DROP CONSTRAINT "T16012941_1__PK"
ALTER TABLE "CDR_WC81_F4566D"."T16012941" MODIFY("C2" NOT NULL)
CREATE UNIQUE INDEX "CDR_WC81_F4566D"."T16012941_1__PK" ON
"CDR_WC81_F4566D"."T16012941" ("C1", "C2", "CDR$CREATION_TS",
"CDR$REAL_DATA_FLAG") TABLESPACE "LSH_WA_DATA" PCTFREE 10 INITRANS 2 MAXTRANS
255 STORAGE ( INITIAL 0K NEXT 0K MINEXTENTS 0 MAXEXTENT
S 0 PCTINCREASE 0) LOGGING
ERROR executing steps
ORA-02220: invalid MINEXTENTS storage option value <=== MINEXTENTS
This is the sequence of events for the recent changes:
1. LSH patch 2468 was applied on top of 2466
2. LOV did not work
3. TMS patch 5013 was applied on top of TMS 501
4. LSH patch 2467 was applied on top of 2468
5. LOV works - but reported 2 issues(for missing un-approved terms and duplicates during LOV search)
however, we did some quick regression today and it looks like none of the LSH jobs(PLSQL, Data mart) work now after this patch. Please find attached the screenshot with error message.
6. Just to check LSH patch 2468 was applied again. But still same issue with all job execution.
Recently upgrade to 188.8.131.52 (184.108.40.206 to 220.127.116.11 and then, 18.104.22.168) and then, started hitting this errors.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms