ADCHECKSEQLIFE.sql and ADCHECKSEQMAX.sql Scripts Do Not Report Lifespan Warnings for Negative Range Sequences
(Doc ID 3039987.1)
Last updated on AUGUST 13, 2024
Applies to:
Oracle Applications DBA - Version 12.2.10 and laterInformation in this document applies to any platform.
Goal
Scripts ADCHECKSEQLIFE.sql and ADCHECKSEQMAX.sql , do not report lifespan warnings about negative range sequences which have a max_value < 0.
These sequences start at the MAX_VALUE (in this scenario , it starts as "-1") , they have a negative increment (-1), and then would run out of range when they reach the MIN_VALUE (Example: Sequence BOM_CTO_ORDER_LINES_S1 has MIN_VALUE of "-2,147,483,647")
So if such a sequence is near its maximum value then it is actually fine, the end of life for such a sequence comes when it reaches the minimum value.
The current scripts do not handle the negative range sequences (listed below) which have the max_value as '-1':
| SEQUENCE_OWNER | SEQUENCE_NAME |
| HR | AME_APPLICATIONS_S |
| HR | AME_TEST_TRANS_S |
| HR | GHR_INTERFACE_2_S |
| BOM | BOM_CTO_ORDER_LINES_S1 |
| CZ | CZ_XFR_PROJECT_BILLS_S |
| JA | JA_CN_ITEM_INTERFACE_S |
| PA | PA_EXPEND_ITEM_ADJ_ACT_S |
About scripts ADCHECKSEQLIFE.sql and ADCHECKSEQMAX.sql:
Reference: Managing Sequences in Oracle E-Business Suite Release 12.2 (Doc ID 2989870.1)
ADCHECKSEQLIFE.sql: To Check Sequence Lifespan Warnings
Use the ADCHECKSEQLIFE.sql script to check for sequence lifespan warnings, including sequences nearing their maximum value limit (that is, where the latest assigned values are above 70% of the maximum value) or limited-range sequences with a large cache size that may cause the sequence to bypass large numbers of values without using them. Sequences shown in this output may run out of available values on your system.
If the ADCHECKSEQLIFE.sql script reports any sequence lifespan warnings, log a service request (SR) with Oracle Support for the associated EBS product. When logging the SR, prefix the the summary of the SR with "SEQ:". Also make sure to include the name of the script, ADCHECKSEQLIFE.sql, and attach the script output. You will work together with the assigned Oracle E-Business Suite Support Representative who will engage Oracle E-Business Suite Development to review your reported SR and provide additional actions as required.
If the script reports any "excessive cache_size" warnings, check the cache size you have set for those sequences. If you increased the cache size for performance tuning purposes, review the effect of the larger cache size on the number gaps for any sequence with a limited maximum value to determine the best cache size for your instance.
Run the script as the APPS user using the following command:
sqlplus APPS @ $AD_TOP/sql/ADCHECKSEQLIFE.sql
Enter password:
ADCHECKSEQMAX.sql : Check Maximum Value Settings
Use the ADCHECKSEQMAX.sql script to check for sequences whose maximum values have been increased beyond the maximum values defined in the current release of Oracle E-Business Suite. Issues detected by the ADCHECKSEQMAX.sql script must be reviewed by Oracle E-Business Suite Support and Development. If the script reports an issue, log a service request (SR) with Oracle Support for the associated EBS product. When logging the SR, prefix the the summary of the SR with “SEQ:”. Also make sure to include the name of the script, ADCHECKSEQMAX.sql, and attach the script output. You will work together with the assigned Oracle E-Business Suite Support Representative who will engage Oracle E-Business Suite Development to review your reported SR and provide next steps as required.
Warning: Do not alter or increase the maximum value of a predefined Oracle E-Business Suite sequence unless Oracle E-Business Suite Development confirms that larger values are supported by the code or a patch is provided by Oracle Support.
Run the script using the following command:
sqlplus <user> @ $AD_TOP/sql/ADCHECKSEQMAX.sql
Enter password:
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |