Welcome to Paul Chuks Oracle dba Professional

 How to quickly resolve archiver error in oracle database 11g, 12c, 19c ORA-00257: archiver error. Connect internal only, until freed. First check the location and size of the archive log location with below command: SQL>  show parameter recovery NAME                                 TYPE        VALUE ------------------------------------ ----------- ------------------------------ db_recovery_file_dest                 string      +FRA db_recovery_file_dest_size            big integer 1000G recovery_parallelism                 integer     0 As you can see, the locations is +FRA inside ASM storage and the size is 1TB. Next check the free space you have available in your ASM location with below query: SQL> select name , total_mb/1024, free_mb/1024 from v$asm_diskgroup; NAME                           TOTAL_MB/1024 FREE_MB/1024 ------------------------------ ------------- ------------ DATA                                212432   133635.047 DBFS_DG                        946.3125   935.1

When audit directory adump get filled, it prevents application from further connection and throw below error : ERROR: ORA-09925: Unable to create audit trail file Linux-x86_64 Error: 28: No space left on device Additional information: 9925 ORA-02002: error while writing to audit trail ORA-09925: Unable to create audit trail file Linux-x86_64 Error: 28: No space left on device Additional information: 9925 At this stage, as a DBA, you need to urgently resolve the issue because everyone will be calling that they cannot access the database. The first thing to do is to check if the file syste is filled up which might not show you 100% because is only the size defined for audit location is reached when you run df -h. However, the inode of the filesystem has reached 100% and that is why it cannot create further login audit files and so could not allow anyone login to the database until the space is freed. To find out if the inode is filled, run df -ih command on the linux syste

https://drive.google.com/file/d/0BwyzpvMqgJ_3YlItckpZWlNaY0E/view?usp=sharing

EM 12c : Agent Raises Periodically Alerts for Target Agent : Internal error detected: java.lang.IllegalStateException:oracle.sysman.gcagent.target.interaction.execution.ConfigStateMgr:798 (Doc ID 1458858.1)

imp \"/ as sysdba\" parfile=imp_filename_dec2014.par file=/filesystem_path/SID/filename_in_dec2014.dmp log=/filesystem_path/SID/imp_filename_dec2014.log fromuser=USERA touser=USERB

The following steps will help you revive an un-responsive KVM on your linux work station.... fixing an unresponsive VM..... 1. Launch a terminal from the linux session... and logon using sudo 2. make sure the VM file is running.. by running #virsh list --all 3. If the VM is not listed under the running VMs, then go to /etc/libvirt/qemu and check if xml file for the affected VM is there 4. check /var/lib/libvirt/qemu/save/ for a copy of the affected vm (vm_name.save) and delete it 5. run virsh start (vm_name) This five short steps can help you save your VM...

Use this query to get the password of the user in the database: select user#, name,password from SYS.user$ where name = '<USERNAME>'; Then use this below to reset the password alter user <username> identified by values '<PASSWORD>';