ORA-1652: unable to extend temp segment by %s in tablespace TEMP
This error occur when user running the queries doesn't get the enough free space in the temporary tablespace to complete the task.
Usually SMON automatically clean up the unused temporary segments so increasing the temporary tablespace is not a good idea in production environment. If this issue is happening on the regular
Being a DBA, you often asked to perform and monitor expdp/impdp - datapump jobs on regular basis. In this post you will get varieties of queries using which you can start, stop, resume, kill and see the status of data pump jobs.
When the export or import job is in progress, you can press +C keys to get to the respective datapump prompt or you can attach to the running job and then issue
The default DBA role is automatically created during Oracle Database installation. This role contains most database system privileges. Therefore, the DBA role should be granted only to actual database administrators. If you want to know which users have been granted the dba role then you need to query the dba_role_privs in the SYS schema.
The DBA role does not include the SYSDBA or SYSOPER
Getting below error while installing oracle 11g/12c database using DBCA.
UnsatisfiedLinkError exception loading native library: njni11
java.lang.UnsatisfiedLinkError: /home/u01/app/oracle/product/11.2.0/db_1/lib/libnjni11.so: libclntsh.so.11.1: cannot open shared object file: No such file or directory
Exception in thread "main" java.lang.UnsatisfiedLinkError: get
Oracle has inbuilt features using which you can convert scn to timestamp and timestamp to scn. SCN_TO_TIMESTAMP takes as an argument a number that evaluates to a system change number (SCN), and returns the approximate timestamp associated with that SCN. This function is useful any time you want to know the timestamp associated with an SCN. In order to do this, Oracle has provided two packages
A materialized view is a table segment or database object that contains the results of a query. A materialized view created with the automatic refresh can not be alter to stop refreshing. In order to disable that you must break the dbms_job that was created in order to refresh the view.
Mview are local copies of data located remotely, or are used to create summary tables based on
Sometimes it is required to flush the single sql plan from the shared pool and it a good idea rather than flushing all the sql plan from the memory. After baselining or fixing the bad plan, DBA's wanted to kick out the sql plan from the memory to confirm, if optimizer is picking the correct plan.
I have seen that many guys simply use to flush the shared pool using alter system flush
There are various ways to describe table in vertica, among some of them are listed below.
List table definition using \d:
=> \d table_name;
=> \d schema_name.table_name;
It will list all the below details:
oraadmin=> \d P1_orahow.u_acct_trans;
List of Fields by Tables
Schema | Table |
Being a DBA, you often asked to check the status of RMAN backup job details. There are many ways to monitor the progress of the backup but you can use the below scripts to monitor the status of the RMAN job like full, incremental & archivelog backups.
You can use views like v$rman_backup_job_details and V$SESSION_LONGOPS to monitor the current executing RMAN jobs and the status of the
Being a DBA, there are many occasions where you need to move all database objects from one tablespace to another to make them reorganized. This is because too many tablespaces consume lot of space and are difficult to manage and cause extra overhead to oracle. So in this situations you need to move tables, indexes and other database objects to the newly created tablesapce.
Recently as a part of