QueryDB

Creation Of Temporary Tables The data in a temporary table is private for the session that created it and can be session-specific or transaction-specific. If the data is to deleted at the end of the transaction the table should be defined as follows: CREATE GLOBAL TEMPORARY TABLE my_temp_table ( column1 NUMBER, column2 NUMBER ) ON COMMIT DELETE ROWS; If on the other hand that data should be preserved until the session ends it should be defined as follows: CREATE GLOBAL TEMPORARY TABLE my_temp_table ( column1 NUMBER, column2 NUMBER ) ON COMMIT PRESERVE ROWS; Export and Import utilities, TRUNCATE, Indexes, Views can be used with/on temporary tables

check constraint (string.string) violated Cause: The values being inserted do not satisfy the named check constraint. Action: Do not insert values that violate the constraint.

integrity constraint - violated - child record Cause: attempted to delete a parent key value that had a foreign key dependency. Action: delete dependencies first then parent or disable constraint.

STOP_QUEUE on string failed, outstanding transactions found cause:-There were outstanding transactions on the queue, and WAIT was set to false, so STOP_QUEUE was unsucessful in stopping the queue. action:-1). Set WAIT to TRUE and try STOP_QUEUE again. It will hang till all outstanding transactions are completed. 2). If you want to stop the queue at once just kill the session using the queue table, and then stop the queue.For this you can take refernce:- kill session stop queue

begin dbms_aqadm.start_queue(queue_name => 'username.tablename'); end; /