ORACLE ERROR : ORA-28000
The account is locked
From your command prompt, type sqlplus “/ as sysdba”
Once logged in as SYSDBA, you need to unlock the SCOTT account
SQL> alter user scott account unlock;
SQL> grant connect, resource to scott;
Posts Tagged ‘oracle error’
ORACLE ERROR:ORA-28000: the account is locked
February 9th, 2026, posted in Oracle QueriesAPP-PAY-06153:System Error. Procedure INIT_FORMS on Step 1
October 4th, 2020, posted in Oracle EBS ApplicationAPP-PAY-06153:System Error. Procedure INIT_FORMS on Step 1
Issue :
APP-PAY-06153:System Error. Procedure INIT_FORMS at Step 1 :
N:->Human Resources->Work Structures->Location
Solution :
N: System Administrator->Profile->System
Click find
Assign Site: FA: Vision Operations
Save and close
N:->Human Resource->Work Structure->Organization
Form is opened
REP-0300: ORACLE Error Occurred In Oracle Reports
March 29th, 2020, posted in Oracle Queries
apps-fnd-01564 oracle error 1653 in summit others
December 22nd, 2019, posted in Oracle QueriesCAUSE :
Typically occurs when writing a new record to oracle database, but there is not enough space to write it. The data file in oracle tablespace called APPS_TS_TX_DATA should be set to AUTOEXTEND. If it is not, Oracle will not auto-increase the size of the datafile, and will raise the above error.
SOLUTION :
If all the reports end in COMPLETE – NORMAL, means its work.
If not than follow below steps.
Run a Concurrent Manager Recovery :
1. Please stop Concurrent managers by adcmctl.sh.
2. If not stopped, please abort managers by adcmctl.sh.
adcmctl.sh abort apps/****
3. Please kill if a process remains.
4. relink all (ADADMIN)
5. Please retry Concurrent Manager Recovery.
Navigate :
Oracle Applications Manager > Concurrent Managers OR Concurrent Requests > Site Map > Diagnostics and Repair > Concurrent Manager Recovery.
OR
SOLUTION :
WARNING: This procedure should be performed by your ORACLE Database Administrator.
The SYSTEM user should have required privileges to perform this task.
Enable Autoextend on the APPS_TS_TX_DATA tablespace by executing the following Oracle PL/SQL command:
SQL > ALTER DATABASE DATAFILE '/u01/ORACLE/ORADATA/APPS_TS_TX_DATA.ORA' AUTOEXTEND ON NEXT 3072K
ORA-19588: archived log RECID 1003 STAMP 2001986 is no longer valid
December 10th, 2019, posted in Oracle QueriesError in RMAN backup log
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on d1 channel at 03/04/2018 23:16:26 ORA-19588: archived log RECID 1003 STAMP 2001986 is no longer valid Recovery Manager complete.
SOLUTION :
This is not an error but a warning. The reason for this is archive logfile which this process is trying to take backup,
is already been backed up by another process and file is deletedThis error is mostly because of 2 reasons :
is already been backed up by another process and file is deletedThis error is mostly because of 2 reasons :
1. Either 2 backups like one full backup and one archive log backup are running in parallel.
And if the archivelog backup job tried to take backup of the archives, which were backed up and deleted by the full back
job running at the same time, then this warning will come.So never schedule two backups at the same time
And if the archivelog backup job tried to take backup of the archives, which were backed up and deleted by the full back
job running at the same time, then this warning will come.So never schedule two backups at the same time
2. Another reason might be because of few invalid or deleted records in control file.
To clean up invalid records, crosscheck the archive log:
RMAN> CROSSCHECK ARCHIVELOG ALL; RMAN> DELETE EXPIRED ARCHIVELOG ALL;
It is recommended to use delete input option while backing up archivelog.
RMAN> backup archivelog until time 'sysdate -1' delete input;
If we want to take backup of all archivelogs, then:
——————————————————————
RMAN> backup archivelog all delete input ;