Skip to Main Content

SQL Developer

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

SQLDeveloper - slow execution of large script

user7425388Mar 26 2021 — edited Mar 26 2021

Hello,
I've quite large SQL script (~11MB) which creates database objects (tables, procedures, functions)
Because script is automatically generated all procedures and function in script are created in alphabetalical order. That's why during script execution I have a lot compiler errors which is totally ok, since at the end of the script I compile all database objects.
Problem is that creation of each procedure/function in SQLDeveloper takes around 5-10 second for each procedure. I think problem is related to fact that SQLDeveloper shows me details of compilation error which I don't need at these time.

Function DPsp_EvalSl compiled

LINE/COL ERROR
----------------------------------------------
21/15 PL/SQL: ORA-00904: "DPsp_Val": invalid identifier
23/17 PL/SQL: ORA-00904: "DPsp_WalSopA": invalid identifier
Errors: check compiler log.
Is there any option in SQLDeveloper to turn off detailed compiler log and speed up execution process a little ?
Regards

Comments

Rafi (Oracle DBA)
Hi ,
For Oracle 11g rel2 there are few changes in auditing.Check the below link for details


2309084



Best regards,

Rafi.
Hemant K Chitale
See the explanation for "BY SESSION" in the 11.2 documentation on the AUDIT command at
http://docs.oracle.com/cd/E11882_01/server.112/e26088/statements_4007.htm#i2059073

In earlier releases, BY SESSION caused the database to write a single record for all SQL statements or operations of the same type executed on the same schema objects in the same session. Beginning with this release of Oracle Database, both BY SESSION and BY ACCESS cause Oracle Database to write one audit record for each audited statement and operation. BY SESSION continues to populate different values to the audit trail compared with BY ACCESS. Oracle recommends that you include the BY ACCESS clause for all AUDIT statements, which results in a more detailed audit record. If you specify neither clause, then BY SESSION is the default.



Hemant K Chitale
1 - 2

Post Details

Added on Mar 26 2021
4 comments
1,560 views