Pin_partition.maxpoid Issue With Setting A Date Format
(Doc ID 2794310.1)
Last updated on AUGUST 28, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
There is an error in pin_partition.maxpoid when setting a date format other than English - more specifically the month name abbreviation, which is hard coded in the English package (01-JAN-1970). The problem may also concern other functions, e.g. pin_rel.purge_batch_rel_objects.
Steps:
alter session set nls_date_language = Polish;
SQL> alter session set nls_date_language = American;
Session altered.
SQL> select TO_DATE('01-JAN-1970', 'DD-MON-YYYY') FROM dual;
TO_DATE('01-JAN
---------------
01-JAN-70
SQL> alter session set nls_date_language = Polish;
Session altered.
SQL> select TO_DATE('01-JAN-1970', 'DD-MON-YYYY') FROM dual;
select TO_DATE('01-JAN-1970', 'DD-MON-YYYY') FROM dual
*
ERROR at line 1:
ORA-01843: not a valid month
SQL> select TO_DATE('28-LUT-2021', 'DD-MON-YYYY') FROM dual;
TO_DATE('28-LUT
---------------
28-LUT-21
SQL>
SQL> alter session set nls_date_language = American;
Session altered.
SQL> select TO_DATE('01-JAN-1970', 'DD-MON-YYYY') FROM dual;
TO_DATE('01-JAN
---------------
01-JAN-70
SQL> alter session set nls_date_language = Polish;
Session altered.
SQL> select TO_DATE('01-JAN-1970', 'DD-MON-YYYY') FROM dual;
select TO_DATE('01-JAN-1970', 'DD-MON-YYYY') FROM dual
*
ERROR at line 1:
ORA-01843: not a valid month
SQL> select TO_DATE('28-LUT-2021', 'DD-MON-YYYY') FROM dual;
TO_DATE('28-LUT
---------------
28-LUT-21
SQL>
After switching to American, reinstated the system behavior correctly.
Please resolve this issue.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |