SCOPE
The article covers common & complex error occurs during the Datapump Export and Import operations
Sharing knowledge is the ultimate key to gaining knowledge…
The only two things that stay with you for life are you & your knowledge...
Live while you can! Teach & inspire while you could & Smile while you have the teeth.
SCOPE
The article covers common & complex error occurs during the Datapump Export and Import operations
SCOPE
Recently a server running both Oracle databases with version 11.1.0.2 had to be forced powered cycled due to a NFS issue. Since it wasn’t possible to login to the O/S to shutdown the DBs an instance recovery was required on both the 11.2 databases.
SCOPE
Application job are running slow and DBA finds out the wait event as "Resmgr:Cpu Quantum" for multiple sessions running in database.
SCOPE
Below script helps to identify the space utilization of Databases including the files such as Datafiles, Redologfiles, Archivelog files on ASM diskgroup categorized by Database names and their files.
SCOPE
Application complains about the error ORA-12519: TNS:no appropriate service handler found while connection to the database.
SCOPE
Restoring
the database using RMAN backup.
After completion of cloning to the staging environment, OPEN RESETLOGS fails with error as below.
ORA-00392: log 1 of thread 1 is being cleared, operation not allowed
SCOPE
Application jobs fails with messages as below.
ORA-20001:
Job failed
ORA-01630: max # extents (4096) reached in temp segment in tablespace USERS
Below document explains the issue faced after the upgrade, troubleshooting and need for timezone files.
At the point when you take a gander at PostgreSQL versus Prophet data set administration frameworks, the primary distinction between these two information bases is that PostgreSQL is an open-source data set, while Oracle is a shut data set framework.
We recently performed the cloning of the staging Database from a production database, but unfortunately we faced an issue.
Once the restore is complete, we were not able to stop the database to rename it and perform the post checks.
Many times when we kill a session with alter system kill session command ( or Toad )
PostgreSQL has native support for using SSL connections to encrypt client/server communications for increased security.
Official documentation : https://www.postgresql.org/download/linux/redhat/
Lets assume that we have an update, insert or delete statement that running but has not been committed yet. So question is how to show uncommitted transactions ?