Run Multiple Queries in Multiple sessions in TOAD

View --> Toad Options -> Oracle --> Transactions -->  Check  Execute queries in threads

This should allow multiple sessions in Toad. Each Session can run its own SQL in parallel.

Comments

Post a Comment

Popular posts from this blog

Create attachments and attach them to Sales Order Header or Order Lines

Use the API below to create the attachment. This could be a limited text that you want on the order header or line. OE_FND_ATTACHMENTS_PUB.CREATE_SHORT_TEXT_DOCUMENT (1.0, --version P_SHORT_TEXT, --Text to be added as attachment P_CATEGORY_ID, -- Attachment category id P_DESCRIPTION, -- Attachment description NULL, V_SECURITY_ID, --The value is 4 for no security NULL, 'Y', 'O', -- One time usage SYSDATE, NULL, NULL, V_DOCUMENT_ID , -- Document id returned by the API V_RETURN_STATUS_CS, V_MSG_COUNT_CS, V_MSG_DATA_CS); Pass V_DOCUMENT_ID from above API into below second API OE_FND_ATTACHMENTS_PUB.ADD_ATTACHMENT (1.0, P_ENTITY_NAME, --Value of this parameter would be 'OE_ORDER_HEADERS' for header level attachment -- and 'OE_ORDER_LINES' for line level attachment P_PK1_VALUE, --line id or header id (For line level or header level attachment) NULL, NULL, NULL, NULL, 'N', NULL, V_DOCUMENT_ID , --Document id from above ap
Read more

Ora 28113 : Policy Predicate has Error

Recently I encountered an Oracle Error. ORA-28113: Policy Predicate has Error After going through so much i decided to write a note about it , so that people who get stuck with this issue can have an option. So i was working on Creating a Materialized View and it is based off of a Select statement which is a Union of bunch of select statements with a bunch of tables and views. So as i try to create the Materialized view with the select statement i built , i was getting the error ORA-28113. After reading a lot of good material online and doing a lot of different things with the sql , finally found out that one of the Object (table) i am using in the SQL had policies. So went to dba_policies table and queried for the table and it had a bunch of policies enabled. So the work around could be either disabling the policies? or trying to create a custom view out of the table  and use the Custom view instead of the base table in the sql statement. Hope this helps people who are in the same
Read more