System Hold, Fix Manager before resetting counters

We have seen this error couple of times in the Concurrent manager Administer screen in our R12.1.3 QA instances.

OPP Concurrent Manager status : System Hold, Fix Manager before resetting counters



Solution:

1. Shutdown the Apps Tier cleanly make sure there are no sessions: 

[applmgr@oracle ~]$ cd $ADMIN_SCRIPTS_HOME

[applmgr@oracle scripts]$ ./adstpall.sh apps/*****


[applmgr@oracle ~]$ ps -ef | grep FNDLIBR
[applmgr@oracle ~]$ ps -ef | grep FNDSM
[applmgr@oracle ~]$ ps -ef | grep FNDCRM
[applmgr@oracle ~]$ ps -ef | grep FNDFS
[applmgr@oracle ~]$ ps -ef | grep applmgr


2. Stop the database.

[ora@oracle  ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.1.0.7.0 - Production on Tue Dec 14 14:28:07 2021

Copyright (c) 1982, 2008, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> shut immediate

3. Start the database.

[ora@oracle ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.1.0.7.0 - Production on Tue Dec 14 14:28:07 2021

Copyright (c) 1982, 2008, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup

4. To the appsTier go to $FND_TOP/bin and run the following relinks.

[applmgr@oracle ~]$ cd $FND_TOP/bin

$ adrelink.sh force=y link_debug=y "fnd FNDLIBR"
$ adrelink.sh force=y link_debug=y "fnd FNDFS"
$ adrelink.sh force=y link_debug=y "fnd FNDCRM"
$ adrelink.sh force=y link_debug=y "fnd FNDSM"

5. Run the CMCLEAN.SQL script and commit..

SQL> @cmclean.sql


6. Execute the following SQL:

SQL> select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';

CONCURRENT_QUEUE_NAME
--------------------------------------------------------------------------------
FNDSM_ORACLE

SQL>

7. Now start the Apps tier:

[applmgr@oracle ~]$ cd $ADMIN_SCRIPTS_HOME

[applmgr@oracle scripts]$ ./adstrtal.sh  apps/*****


Check status of OPP Concurrent manager.

I hope issue got fix.



ORA-06512: at "APPS.FND_CP_GSM_IPC"

 Unable to Start “Output Post Processor” Concurrent Manager

After starting concurrent manager I noticed "Output Post Processor" did not start. I tried to start "Output Post Processor" using "Administrator Concurrent Manager" screen but it failed with given error in manager log file


OPP Manager Log

Unable to initialize state monitor.

oracle.apps.fnd.cp.gsm.GenCartCommException: ORA-01422: exact fetch returns more than requested number of rows

ORA-06512: at "APPS.FND_CP_GSM_IPC", line 539

ORA-06512: at line 1

at oracle.apps.fnd.cp.gsm.GenCartComm.initService(GenCartComm.java:233)

at oracle.apps.fnd.cp.gsm.GenCartComm.<init>(GenCartComm.java:80)

at oracle.apps.fnd.cp.gsf.GSMStateMonitor.init(GSMStateMonitor.java:74)

.0002730 secs]

[GC 3338K->1928K(4992K), 0.0002350 secs]


Solution:

Checked and found "Service Manager" was down.

Started "Service Manager" and then started "Output Post Processor".

ORA-04033: Insufficient memory to grow pool

 I am trying to expand by shared_pool size and I get the below error.

ERROR:-

SQL> alter system set streams_pool_size =300M scope=both;

alter system set streams_pool_size =300M scope=both

ERROR at line 1:

ORA-02097: parameter cannot be modified because specified value is invalid

ORA-04033: Insufficient memory to grow pool


Verify:-

 you do not have enough RAM allocated to the SGA to allow you to create a 300M shared pool. 

[root@ora ~]# free -g

              total        used        free      shared  buff/cache   available

Mem:             14           9           1           0           3           2

Swap:            15           2          13

[root@ora ~]#

SQL> show parameter sga_max_size;


NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

sga_max_size                         big integer 1G

SQL>


Solution :-

Specify a smaller value to grow the pool.

SQL> alter system set streams_pool_size =200M scope=both;

System altered.


SQL> show parameter streams_pool_size;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
streams_pool_size                    big integer 200M
SQL>




 




Queries to Monitor Expdp Jobs Status

 

1. How to check the progress of  export or import Jobs

SQL > SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS;

2. Finding the Datapump Job Status from V$SESSION_LONGOPS

SQL > SELECT B.USERNAME, A.SID, B.OPNAME, B.TARGET,

            ROUND(B.SOFAR*100/B.TOTALWORK,0) || '%' AS "%DONE", B.TIME_REMAINING,

            TO_CHAR(B.START_TIME,'YYYY/MM/DD HH24:MI:SS') START_TIME

     FROM V$SESSION_LONGOPS B, V$SESSION A

     WHERE A.SID = B.SID    

  AND B.OPNAME LIKE '%EXPORT%'

   ORDER BY 6;

3. To monitor executing jobs using dba_datapump_jobs view:

SQL > SELECT 

owner_name, 

job_name, 

operation, 

job_mode, 

state 

FROM 

dba_datapump_jobs

where state='EXECUTING';

4. To get the detail information like SID, Serial#, and % of completion:

SQL > SELECT 

OPNAME, 

SID, 

SERIAL#, 

CONTEXT, 

SOFAR, 

TOTALWORK,

    ROUND(SOFAR/TOTALWORK*100,2) "%_COMPLETE"

FROM 

V$SESSION_LONGOPS

WHERE 

OPNAME in

(

select 

d.job_name

from 

v$session s, 

v$process p, 

dba_datapump_sessions d

where 

p.addr=s.paddr 

and 

s.saddr=d.saddr

)

AND 

OPNAME NOT LIKE '%aggregate%'

AND 

TOTALWORK != 0

AND 

SOFAR <> TOTALWORK;


5. To check the waiting status and wait event of the job waiting for:


SQL > SELECT   w.sid, w.event, w.seconds_in_wait

   FROM   V$SESSION s, DBA_DATAPUMP_SESSIONS d, V$SESSION_WAIT w

    WHERE   s.saddr = d.saddr AND s.sid = w.sid;

SQL > select username,opname,target_desc,sofar,totalwork,message from V$SESSION_LONGOPS;


7. The percentage of work done

SQL > SELECT b.username, a.sid, b.opname, b.target,

            round(b.SOFAR*100/b.TOTALWORK,0) || '%' as "%DONE", b.TIME_REMAINING,

            to_char(b.start_time,'YYYY/MM/DD HH24:MI:SS') start_time

     FROM v$session_longops b, v$session a

     WHERE a.sid = b.sid      ORDER BY 6;


SQL> select COMMAND,STATE,WAIT_CLASS,EVENT,SECONDS_IN_WAIT from v$session where sid=57 and SERIAL#=40478;

To check the orphaned datapump jobs. For orphaned jobs the state will be NOT RUNNING.

SQL> SELECT owner_name, job_name, operation, job_mode,

state, attached_sessions FROM dba_datapump_jobs;


To check the alert log and query the DBA_RESUMABLE view.

SQL > select name, sql_text, error_msg from dba_resumable;


To kill the datapump jobs:

SQL > alter system kill session 'SID,SERIAL#' immediate;


Check running EXPDP status.

$ expdp system/******@CDB attach=SYS_EXPORT_SCHEMA_04

[oracle@ora]$ expdp system/******@CDB attach=SYS_EXPORT_SCHEMA_04

Export: Release 12.2.0.1.0 - Production on Wed Dec 1 14:11:21 2021

Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

Job: SYS_EXPORT_SCHEMA_04

  Owner: SYSTEM

  Operation: EXPORT

  Creator Privs: TRUE

  GUID: ABSCDNMVJBK

  Start Time: Wednesday, 01 December, 2021 19:03:20

  Mode: SCHEMA

  Instance: CDB

  Max Parallelism: 0

  Timezone: +00:00

  Timezone version: 28

  Endianness: LITTLE

  NLS character set: AL32UTF8

  NLS NCHAR character set: AL16UTF16

  EXPORT Job Parameters:

  Parameter Name      Parameter Value:

     CLIENT_COMMAND        system/********@CDB schemas=SONU directory=SONU dumpfile=SONU.dmp logfile=SONU.log reuse_dumpfiles=true

     TRACE                 0

  State: DEFINING

  Bytes Processed: 0

  Job Error Count: 0

  Job heartbeat: 1


Export> status

Job: SYS_EXPORT_SCHEMA_04

  Operation: EXPORT

  Mode: SCHEMA

  State: DEFINING

  Bytes Processed: 0

  Job Error Count: 0

  Job heartbeat: 1


Export>


================================================================

References:-

http://www.runningoracle.com/product_info.php?products_id=390

DataPump Export/Import Hangs With "DEFINING" Status When Using A Directory On NFS Filesystem (Doc ID 2262196.1)

Data Pump Hanging When Exporting To NFS Location (Doc ID 434508.1)

=====================================================





How to Check the table Size in Oracle.

To check table name segment type and table size in MB 

SQL> select segment_name,segment_type,bytes/1024/1024 MB from dba_segments where segment_type='TABLE' and segment_name='sujeet'

             SEGMENT_NAME         SEGMENT_TYPE                      MB

           -------------------- ------------------ ---------------------------------------

             sujeet                                 TABLE                                          192


To check Table Owner,Table Name and Table Size.

You can check here one SYSTEM owner have multiple tables with different sizes and names.

SQL> select owner,segment_name,sum(bytes)/1024/1024/1024 as "SIZE in GB" from dba_segments where owner='SYSTEM' and segment_type='TABLE' group by owner,segment_name order by                  "SIZE in GB" desc;


OWNER                          SEGMENT_NAME         SIZE in GB              

------------------------------ ---------------------------------------------------------------            

SYSTEM                                 SONU                  1.50683594              

SYSTEM                                 Aasu                  .984375              

SYSTEM                                BIHAR                   .921875      


SQL > select owner,segment_name,sum(bytes)/1024/1024/1024 as "SIZE in GB" from dba_segments

where owner='SCOT' and segment_type='TABLE' group by owner,segment_name order by "SIZE in GB" desc;

SQL >  select owner,segment_name,sum(bytes)/1024/1024/1024 as "SIZE in GB" from dba_segments

where owner='SCOT' and segment_type='LOBSEGMENT' group by owner,segment_name order by "SIZE in GB" desc;



ORA-01000: maximum open cursors exceeded

 Error in application log file.


<PRE>SQL_PLSQL_ERROR &#40;ERRNO=604&#41; &#40;REASON=java.sql.SQLException: ORA-00604: error occurred at recursive 

SQL level 1 ORA-01000: maximum open cursors exceeded ORA-00604: 

error occurred at recursive SQL level 1 ORA-01000: maximum open cursors exceeded ORA-01000: maximum open cursors 

exceeded ORA-06512: at &#34;APPS.FND_SESSION_UTILITIES&#34;, line 37 ORA-06512: at line 1

 &#41; &#40;ROUTINE=decryptSessionCookie&#40;String&#41;&#41; ICX_SESSION_FAILED </PRE>

Servlet error: An exception occurred. The current application deployment descriptors do not allow for 

including it in this response. Please consult the application log for details.

                                        Solution

To troubleshoot the open cursors issue:


Login to the SYS schema (or any schema with DBA privilege) of the database.

Find out the session that is causing the error by using the following SQL statement:


SQL> SELECT  max(a.value) as highest_open_cur, p.value as max_open_cur FROM v$sesstat a, v$statname b, v$parameter p WHERE  a.statistic# = b.statistic#  and b.name = 'opened cursors current' and p.name= 'open_cursors' group by p.value;

HIGHEST_OPEN_CUR---------------- MAX_OPEN_CUR

              600                                                 600


SQL> SELECT value FROM v$parameter WHERE name = 'open_cursors';


VALUE

--------------------------------------------------------------------------------

600


Increase open_cursors value 600 to 1000.

LOgin with SYSDBA

$ sqlplus / as sysdba

SQL> alter system set open_cursors = 1000 scope=both;

System altered.

SQL> commit;

Commit complete.

SQL> SELECT value FROM v$parameter WHERE name = 'open_cursors';

VALUE

--------------------------------------------------------------------------------

1000


SQL> create pfile from spfile;

File created.

SQL> shut immediate

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL>

SQL> startup

ORACLE instance started.

Total System Global Area 7482626048 bytes

Fixed Size                  2160752 bytes

Variable Size            1677723536 bytes

Database Buffers         5771362304 bytes

Redo Buffers               31379456 bytes

Database mounted.

Database opened.

SQL> SELECT value FROM v$parameter WHERE name = 'open_cursors';

VALUE

--------------------------------------------------------------------------------

1000


Find which SQL is using more cursors


SQL> select a.value, s.username, s.sid, s.serial# from v$sesstat a, v$statname b, v$session s where a.statistic# = b.statistic#  and s.sid=a.sid and b.name = 'opened cursors current' and s.username is not null;

     VALUE USERNAME               SID    SERIAL#

---------- ------------------------------ ---------- ----------

        47 APPS                                  358        134

        63 APPS                                  365        160

        88 APPS                                  453         12

        51 APPS                                  459         17


SQL> SELECT  max(a.value) as highest_open_cur, p.value as max_open_cur FROM v$sesstat a, v$statname b, v$parameter p WHERE  a.statistic# = b.statistic#  and b.name = 'opened cursors current' and p.name= 'open_cursors' group by p.value;


HIGHEST_OPEN_CUR----------------MAX_OPEN_CUR

             102                                                     1000




Alert and Listener log path in Oracle 12C database

                        Alert log text file path in 12C

1. Find diag location

SQL> SELECT name,VALUE FROM V$DIAG_INFO where name = 'Diag Alert';

NAME       VALUE

---------- -----------------------------------------

Diag Alert  /u01/app/oracle/diag/rdbms/host_SID/SID/alert


2. For text file move to trace folder instead of alert folder.

/u01/app/oracle/diag\rdbms\xe\xe\trace


SQL> Show parameter background_dump_dest

NAME                   TYPE        VALUE

---------------------- ----------- ------------------------------

background_dump_dest   string      /u01/app/oracle\DBHOMEXE\RDBMS\TRACE


Listener log path

1. Find the diag parameter location

SQL> show parameter diag

NAME              TYPE        VALUE

----------------- ----------- -------------

diagnostic_dest   string      /u01/app/oracle


2. For text file:

$DIAG_LOCATION   /u01/app/oracle\listener\trace\listener.log


3. For XML File:

$DIAG_LOCATION    /u01/app/oracle\listener\alert\log.xml


You get the listener log location with lsnrctl status command

$LSNRCTL status

How to Enable Database Management for Oracle Cloud Databases

 

Please follow below link for Enable Database Management for Oracle Cloud Databases

https://database-heartbeat.com/2021/09/13/enable-db-mgmt/

https://docs.oracle.com/en-us/iaas/database-management/doc/permissions-required-database-management.html#DBMGM-

https://docs.oracle.com/en-us/iaas/database-management/doc/perform-database-management-prerequisite-tasks.html#GUID-BF854DE9-2EB9-4333-B3BF-C164F16A2A1B

https://docs.oracle.com/en-us/iaas/database-management/doc/perform-database-management-prerequisite-tasks.html#DBMGM-GUID-C0C28FF3-12E3-4D45-9ED5-B06B2EF52978

https://docs.oracle.com/en-us/iaas/Content/API/Concepts/cloudshellgettingstarted.htm





Output Post Processor Down : Actual 0 Target 3

“Output Post Processor” Concurrent Manager not able to start

OPP manager log file path :- /u01/apps/inst/apps/QA_QA01/logs/appl/conc/log

[qa1@QA01 log]$ ls -lrt |grep FNDOPP

Error in OPP log file.

[qa1@QA01 log]$ cat FNDOPP2127409.txt

Unable to initialize state monitor.

oracle.apps.fnd.cp.gsm.GenCartCommException: ORA-01422: exact fetch returns more than requested number of rows

ORA-06512: at "APPS.FND_CP_GSM_IPC", line 539

ORA-06512: at line 1

        at oracle.apps.fnd.cp.gsm.GenCartComm.initService(GenCartComm.java:233)

        at oracle.apps.fnd.cp.gsm.GenCartComm.<init>(GenCartComm.java:80)

        at oracle.apps.fnd.cp.gsf.GSMStateMonitor.init(GSMStateMonitor.java:74)

        at oracle.apps.fnd.cp.gsf.GSMStateMonitor.<init>(GSMStateMonitor.java:62)

        at oracle.apps.fnd.cp.gsf.GSMServiceController.init(GSMServiceController.java:111)

        at oracle.apps.fnd.cp.gsf.GSMServiceController.<init>(GSMServiceController.java:66)

        at oracle.apps.fnd.cp.gsf.GSMServiceController.main(GSMServiceController.java:428)

.0002460 secs]


                                                          SOLUTION


1. Shutdown the internal manager by using adcmctl.sh stop apps/****
2. Make sure there is no FNDLIBR processe running:
            $ ps -ef| grep FNDLIBR 
3. If there is any FNDLIBR processe please kill it $ kill -9 pid
4. Run cmclean.sql script as document from Note 134007.1
5. Restart the internal manager by using adcmctl.sh start apps/*****

Retest issue. I hope issue has been resolved.


                                             OR 

For performance issue please increase java heap size

Maximum Memory Usage Per Process:


The maximum amount of memory or maximum Java heap size a single OPP process can use is by default set to 512MB. 

This value is seeded by the Loader Data File: $FND_TOP/patch/115/import/US/afoppsrv.ldt which specifies that the 

DEVELOPER_PARAMETERS is “J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m”.


How to determine the current maximum Java heap size:

SELECT service_id, service_handle, developer_parameters

FROM fnd_cp_services

WHERE service_id = (SELECT manager_type

FROM fnd_concurrent_queues

WHERE concurrent_queue_name = ‘FNDCPOPP’);SERVICE_ID SERVICE_HANDLE DEVELOPER_PARAMETERS

———- ————– ——————————————————–

1091 FNDOPP J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m


Increase the maximum Java heap size for the OPP to 1024MB (1GB):


UPDATE fnd_cp_services

SET developer_parameters =

‘J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m’

WHERE service_id = (SELECT manager_type

FROM fnd_concurrent_queues

WHERE concurrent_queue_name = ‘FNDCPOPP’);


The OPP queue can be Recreated the using $FND_TOP/patch/115/sql/afopp002.sql file as ‘APPLSYS’ user. 


OPP Running process status.

SQL> select sid,serial#,status,logon_time,module from v$session where module like'%OPP%';

SID SERIAL# STATUS LOGON_TIM MODULE
--- ------- ------- --------- ------
5769 31 ACTIVE 14-APR-15 FNDCPOPP

5773 10 ACTIVE 14-APR-15 FNDCPOPP

5780 4 ACTIVE 14-APR-15 FNDCPOPP


Check from front end.

Actual and Target processes should both be 3.






GRANT statement

Syntax for GRANT statement

 

GRANT SELECT ON all_objects to <Schema_name>;

GRANT EXECUTE ANY PROCEDURE to <Schema_name>;

GRANT CONNECT TO <Schema_name>;

GRANT RESOURCE TO <Schema_name>;

ALTER USER <Schema_name> DEFAULT ROLE ALL;

GRANT SELECT ANY TABLE TO <Schema_name>;

GRANT CREATE SESSION TO <Schema_name>;

GRANT CREATE TRIGGER TO <Schema_name>;

GRANT CREATE ANY VIEW TO <Schema_name>;

ALTER USER <Schema_name> QUOTA UNLIMITED ON <Schema_name>;

grant create any procedure to <Schema_name>;

grant create table to <Schema_name>;

grant create view, create procedure, create sequence to <Schema_name>;

GRANT DROP ANY TABLE to <Schema_name>;

GRANT DELETE ANY TABLE to <Schema_name>;

GRANT INSERT ANY TABLE to <Schema_name>;

GRANT UPDATE ANY TABLE to <Schema_name>;

GRANT EXECUTE ANY PROCEDURE to <Schema_name>;

GRANT CREATE ANY SEQUENCE to <Schema_name>;

GRANT CREATE SYNONYM to <Schema_name>;

grant create any index to <Schema_name>;

GRANT READ ANY TABLE TO <Schema_name>;

GRANT SELECT ANY DICTIONARY TO <Schema_name>;

GRANT CREATE TRIGGER TO <Schema_name>;

GRANT SELECT ANY TABLE TO <Schema_name>;

GRANT CREATE ANY VIEW TO <Schema_name>;


For example, if we want our books_admin user to have the ability to perform 

SELECT, UPDATE, INSERT, and DELETE capabilities on the books table, 

we might execute the following GRANT statement:

GRANT SELECT,INSERT,UPDATE ON <Schema_name>.Table_name TO <Schema_name>;


ORA-02020: too many database links in use


Cause:  The current session has exceeded the INIT.ORA open_links maximum.


Solution :-

SQL> show parameter open_links;

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

open_links                           integer              0

open_links_per_instance              integer     4


[oracle@ora ~]$ sqlplus sys/****@PDB as sysdba

SQL*Plus: Release 12.2.0.1.0 Production on Fri Oct 15 14:37:19 2021

Copyright (c) 1982, 2016, Oracle.  All rights reserved.

Last Successful login time: Fri Oct 15 2021 14:37:01 -04:00

Connected to:

Oracle Database 12c EE High Perf Release 12.2.0.1.0 - 64bit Production


SQL> shut immediate

Pluggable Database closed.

SQL> startup

Pluggable Database opened.

SQL> show parameter open_links;


NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

open_links                           integer              4

open_links_per_instance              integer     4

SQL>


PLS-00201: identifier 'AD_JAR.GET_JRIPASSWORDS' must be declared

 ADADMIN With Error "PLS-00201: identifier 'AD_JAR.GET_JRIPASSWORDS' must be declared"

While running ADOP / ADPATCH the below error occurs:

The ORACLE username specified below for Application Object Library

uniquely identifies your existing product group: APPLSYS

Enter the ORACLE password of Application Object Library [APPS] : *****

AutoPatch is verifying your username/password.

Connecting to APPS......Connected successfully.

Error: Unable to execute statement <

Begin

ad_jar.get_jripasswords(:l_storepass, :l_keypass);

End;

> len = 63

AutoPatch error:

ORA-06550: line 3, column 1:

PLS-00201: identifier 'AD_JAR.GET_JRIPASSWORDS' must be declared

ORA-06550: line 3, column 1:

PL/SQL: Statement ignored

AutoPatch error:

Unable to get passwords from Vault

Possible Reasons:

The AD_JAR object not available in apps schema.

 SQL> desc AD_JAR

ERROR:

ORA-04043: object AD_JAR does not exist

Solution:

1. Please login as applmgr (Unix user that own application binaries )

2. Source the application environment file . (APPS.env)

3. cd $AD_TOP/patch/115/sql/

4. Login to database as apps database user and run below 2 SQL's

@ADJRIS.pls

@ADJRIB.pls

5. Run the below SQL to see whether objects are valid

select owner,object_type,status from dba_objects where object_name='AD_JAR';

Set Oracle User password never expired in 12C database?

ERROR:

ORA-28002: the password will expire within 7 days

ERROR at line 1:

ORA-28007: the password cannot be reused

Solution :-

 SQL> select username, account_status, EXPIRY_DATE from dba_users where username='SYSTEM';

SQL> select profile from DBA_USERS where username = 'HR';

SQL> SELECT * FROM dba_profiles WHERE profile = 'DEFAULT' AND resource_type = 'PASSWORD';

Next, change the profile limit to unlimited.

SQL> alter profile DEFAULT limit PASSWORD_REUSE_TIME unlimited;

SQL> alter profile DEFAULT limit PASSWORD_REUSE_MAX unlimited;

SQL> alter profile DEFAULT limit PASSWORD_LIFE_TIME  unlimited;

SQL> ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS 100 PASSWORD_LOCK_TIME 100;

SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_GRACE_TIME unlimited;

-------------------------------------------------------------------------

SQL> alter user HR account lock;

SQL> select USERNAME,ACCOUNT_STATUS,LOCK_DATE,EXPIRY_DATE,LAST_LOGIN from dba_users where USERNAME='HR';

SQL> select LIMIT, RESOURCE_NAME from dba_profiles where RESOURCE_NAME in ('PASSWORD_GRACE_TIME','PASSWORD_LIFE_TIME','PASSWORD_REUSE_MAX','PASSWORD_REUSE_TIME') and PROFILE=(select profile from dba_users where username='SYSTEM');

LIMIT           RESOURCE_NAME

UNLIMITED PASSWORD_LIFE_TIME

UNLIMITED PASSWORD_REUSE_TIME

UNLIMITED PASSWORD_REUSE_MAX

UNLIMITED       PASSWORD_GRACE_TIME

For development you can disable password policy if no other profile was set (i.e. disable password expiration in default one):

SQL> ALTER PROFILE "DEFAULT" LIMIT PASSWORD_VERIFY_FUNCTION NULL;

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

create a new policy and assign that to your users:

SQL> create profile unlimited_password_policy limit password_life_time unlimited;

SQL> alter user <username> profile unlimited_password_policy;

SQL> ALTER PROFILE unlimited_password_policy LIMIT PASSWORD_GRACE_TIME unlimited;

Oracle E-Business Suite 12.2.10 Now Available

 Many new features and enhancements were requested and voted on by customers using the social media capabilities of the Oracle E-Business Suite Communities on My Oracle Support. Other new features and enhancements reflect continued development of themes introduced in earlier 12.2 releases, including functional innovation, user interface modernization, and increased operational efficiency.

For details regarding the EBS 2020 innovations, see:

The EBS 12.2.10 release update pack (RUP) is delivered on My Oracle Support as Patch 30399999.  Instructions for downloading and applying this latest RUP on top of the EBS 12.2 codeline can be found here:

What Does Release 12.2.10 Include?

As a consolidated suite-wide patchset, this RUP includes new features, statutory and regulatory updates, and enhancements for stability, performance, and security.

Release 12.2.10 is cumulative. That means that as well as providing new updates for this release, it also includes updates that were originally made available as one-off patches for earlier 12.2 releases.

For a complete list of new features, refer to:

Common Questions and Answers About Upgrading

  • Q: Is there a direct upgrade path from EBS 12.2.x to 12.2.10?
  • A: Yes. Release 12.2.x customers can apply 12.2.10 directly to their environments. EBS 12.2.10 is an online patch, so it can be applied while an existing Release 12.2.x system is running.
  • Q: Is there a direct upgrade path from Release 12.1 to Release 12.2.10?
  • A: No. Release 12.1 customers must first upgrade to Release 12.2 before applying 12.2.10.
            • Q: Is there a direct upgrade path from Release 12.0 to Release 12.2.10?
            • A: No. Release 12.0 customers must first upgrade to Release 12.2 before applying 12.2.10.
            • Q: Is there a direct upgrade path from EBS 11i to 12.2.10?
            • A: No. Release 11i customers must first upgrade to Release 12.2 before applying 12.2.10.

            Additional References


            What is Oracle EBS 12.2.10?

            EBS 12.2.10 is Oracle’s most recent iteration of the E-Business Suite collection of software applications for enterprise resource planning, customer relationship management, and supply chain management. The previous version, EBS 12.2.9, was released last year in August 2019.

            This release schedule is in line with Oracle’s EBS roadmap, which aims to deliver a new EBS patch on an annual basis. Oracle also plans to issue an upcoming “12.X” version of EBS which will be supported through at least 2030, although details at this point are hazy.

            What’s New in Oracle EBS 12.2.10?

            With that said, what are the new features in EBS 12.2.10?

            EBS 12.2.10 is a cumulative patch, which means that it includes both new features and updates that were part of previous 12.2 patches. According to Oracle product management director Elke Phelps, many of the new EBS 12.2.10 features were requested and voted on by EBS customers, while others have been in the pipeline as part of Oracle’s overarching goals of improving operational efficiency and modernizing the user interface.

            Just a few of the most anticipated new features of EBS 12.2.10 are:

            • Order management: Oracle iStore uses Enterprise Command Center technology to “provide a modern user experience in B2B shopping.” The Performance Evaluation Dashboard in the Oracle Incentive Compensation Command Center lets administrators view employees’ sales attainment and performance across different roles, plans, and periods.
            • Logistics:2.10 has made significant updates to the Receiving Dashboard, Reservations Dashboard, and Reservations HTML UI. For example, the Receiving Dashboard allows users to track material by “Expected Date,” track pending inspections, manage pending putaways, and much more. Oracle Warehouse Management (WMS) has added various enhancements, e.g. creating optimized travel paths for pickers to finish their work with a single pass through the warehouse.
            • Procurement: As with Order Management, Oracle iStore now has “an enhanced consumer-like shopping experience”. The Employee Shopping Tracker in the Oracle Procurement Command Center helps improve catalog content by tracking employees’ shopping searches.
            • Projects:2.10 includes more accurate financial management for U.S. federal trading partners, with support for G-Invoicing (government invoicing).
            • The 12.2.10 features listed above really are just the tip of the iceberg—there are also various improvements to asset lifecycle management, human capital management, financial management, and more. For the full list of new features in EBS 12.2.10, check out Oracle’s document “Announcing Oracle E-Business Suite: Innovations in 2020.”

              Upgrading to Oracle EBS 12.2.10

              Keeping your EBS deployment up-to-date is crucial—especially if you’re using Oracle EBS 12.1, which is scheduled to end Premier Support next year. (Still using EBS 12.1? Check out our white paper “Time is Running Out for Oracle EBS 12.1 – Here’s What You Can Do.”)

              If you’re already on EBS 12.2, you can install 12.2.10 through My Oracle Support as Patch 30399999. The good news is that 12.2.10 is an online patch, i.e. you can keep your EBS deployment running while it installs. You can find detailed instructions for applying the 12.2.10 patch here.

              If you’re not yet on EBS 12.2, however, you won’t yet be able to install 12.2.10 by itself (and it’s high time that you start planning for an upgrade). You’ll first have to upgrade to a EBS 12.2.x version, and then install the 12.2.10 patch.

              Looking for some help? As an Oracle Platinum Partner with 17 different specializations in Oracle products, Datavail has helped countless clients enjoy the latest features and bug fixes by upgrading their Oracle deployments. Get in touch with Datavail’s team of Oracle experts today to chat about your business needs and objectives.

            What’s the latest Oracle E-Business Suite Release/support update?

            This summary page is intended to provide the following information:

            1. Which Oracle support policy applies to the various Oracle E-Business Suite components and where to find the official Oracle support policy documents and error correction support documents

            1.  Which support policy applies and where to find it

            Oracle E-Business Suite deployments include the Oracle E-Business Suite Release, the 

            Oracle E-Business Suite internal application tier technology stack, the Oracle E-Business Suite 

            database and optional external integrations.

            The following table includes guidance regarding which support policy applies to the various components of your EBS deployment and the location of the support policy documents:

            Support Time LineCovered ComponentsWhere to Find the Official Support Policy Documents
            Oracle E-Business Suite
            • Oracle E-Business Suite Release
            • Oracle E-Business Suite Internal Application Tier Technology Stack

            Oracle Lifetime Support Policy: Oracle Applications

            Tip:  Search for E-Business Suite in the referenced document

            DatabaseAll Oracle Databases including the Oracle E-Business Suite Database

            Oracle Lifetime Support Policy:  Oracle Technology Products

            Tip:  Search for Oracle Database Releases in the referenced document

            Fusion Middleware

            All Fusion Middleware products including those used for external integrations with EBS

            Examples:  SOA Suite, OAM, OID, OUD, etc.

            Oracle Lifetime Support Policy:  Oracle Fusion Middleware Products
             

            For dates of grace periods for Oracle database releases, see:  Release Schedule of Current Database Releases (MOS Note 742060.1).  Here is an excerpt:

            Oracle Database ReleaseSupport Dates

            19c

            End of Premier Support:  April 30, 2024 or April 30, 2027 with paid Extended Support (ES)
            12.1.0.2End of Error Correction Support: July 31, 2022 with ES or Universal License Agreement (ULA) - (not all platforms)
            11.2.0.4

            End of  Market Driven Support (MDS): December 31, 2022

            Error Correction Support Ended: December 31, 2020 

            Note: 

            • All older database releases are out of Error Correction Support
            • For Oracle Database 12.1 there is a global ES fee waiver in place for E-Business customers. For additional details and the process to determine your eligibility, see: Extended Support Fee Waiver or Oracle E-Business Suite (MOS Note 2522948.1)

            For dates of grace periods for specific Fusion Middleware releases see:

            2. Certifications for Current Oracle E-Business Suite Releases and Components

            IMPORTANT:  The source of truth for certifications is maintained on My Oracle Support.  If in doubt, always check the Certifications database for the final word.

            This summary page cross-references published blog articles and the official certifications listed in the Certifications database on My Oracle Support.  Platform-specific information is available in the Certifications database on My Oracle Support.

            Obsolete certifications are releases that are no longer eligible for Extended Support or Error Correction Support. Obsolete certifications are denoted on this page using the following symbol: 

            Obsolete certifications that have been archived from this page are available for reference on the following page:  Obsolete EBS Certifications

            Current EBS Releases

             EBS 12.2EBS 12.1

            Support
            Dates

            Premier Support to At Least December 2032

            April 2021 Announcement

            Premier Support to December 2021

            Beginning January 1, 2022, Market-Driven Support for EBS 12.1 is an option

            Release
            Update
            Packs

            12.2.10 (09/2020)

            12.2.9 (08/2019)

            12.2.8 (10/2018)

            12.2.7 (9/2017)

            12.2.6 (9/2016)

            12.2.5 (10/2015)

            12.2.4 (8/2014)

            12.2.3 (12/2013)

            12.1.3 RPC5 (8/2016)

            12.1.3 RPC4 (10/2015)

            12.1.3 RPC3 (4/2015)

            12.1.3 RPC2 (9/2014)

            12.1.3 RPC1 (3/2014)

            12.1.3 (8/2010)

            12.1.2 (12/2009)

            Initial
            Release

            12.2.2 (9/2013)

            12.1.1 (4/2009)

            Documentation

            Web Library

            EBS 12.2 Technology Stack Doc Roadmap

            Web Library

            EBS 12.1 Technology Stack Doc Roadmap

             

            EBS 12.2:  Internal Application Tier Technology Stack Certifications

            • Forms 10.1.2.3
            • WLS 11gR1 Patchset 5 (10.3.6)
            • WebTier Utilities: 11.1.1.9[ 11.1.1.6 , 11.1.1.7]
            • Java SE (JDK) 7 , [6]

            EBS 12.1:  Internal Application Tier Technology Stack Certifications

            EBS 12.2, 12.1:  Database Certifications

            EBS 12.2, 12.1:  Optional External Integrations

            Oracle Enterprise Manager Cloud Control 13c

            EBS 12.2, 12.1:  Client Certifications

            Java Runtime Environment

            All JRE 1.7 and 1.8 updates are automatically certified with all supported EBS releases

            Windows 

            Windows-based Browsers

            Windows-based Office

            Apple Mac OS X and iOS

            Other EBS Certifications


            Reference link :- https://blogs.oracle.com/ebstech/ebs-resources


            ORA-01552: cannot use system rollback segment for non-system tablespace 'TEMP'

             ORA-01552: cannot use system rollback segment for non-system tablespace "string" Cause: Used the system rollback segment for non...