When there are too many SQL commands (the SQL file is too large), the execution of PLSQL is slow and easy to timeout. At this time, you can directly execute the SQL script file with sqlplus command, as follows:
1. Sqlplus login
> sqlplus username/ password@dbname
2. Execute SQL file
If the SQL file is in the current directory, you can directly execute:
>@ demo.sql
If the SQL file is not in the current directory, you can use the absolute path:
>@ D:/demo.sql
Similar Posts:
- Error handling of PLSQL initial login to Oracle
- Git Error: Github:remote: Invalid username or password……
- Linux cron has no effect after executing the script, and the log reports an error orphan (no passwd entry)
- [Solved] Linux Oracle bash: “sqlplus / as sysdba”: command not found
- [Solved] Error resolving template “XXX”, template might not exist or might not be accessible by any of the
- Elasticsearch + kibana set user name and password to log in
- Trouble Connecting to sql server Login failed. “The login is from an untrusted domain and cannot be used with Windows authentication”
- The Chrome browser cannot remember the password and does not prompt to save the password win10 [How to Solve]
- How to Solve ra-28000 account being locked Error
- An error is reported when logging into harbor warehouse with docker login of other hosts