Common problems and troubleshooting in ORACLE database application development
- 2020-05-17 06:50:13
- OfStack
The ORACLE tutorial you are looking at is :ORACLE database application development FAQ and troubleshooting. Hardware platform: SUN Ultra Enterprise 3000
Operating system: Solaris 2.5(simplified Chinese)
Disk: 4.2 GB
Memory: 256 MB
ORACLE B version: 7.3.2.1
Installation directory: /database/oracle (2GB space under /database)
Installation products: ORACLE RDBMS,SQL * NET,SQL * Plus,Pro * C,Server Manager, etc
The product is installed normally and running stably.
2. Common problems in application development and elimination
In the process of application development, the ORACLE database often encounters the following two problems:
1. You cannot close the database with Shutdown;
2. The Client terminal often crashes without any reason.
Elimination of problem 1: as long as the correct command is used to open and close the database (only Internal users have the right), problem 1 occurs because the database has uncommitted transactions. The Shutdown Abort command can be used to close the database, but all uncommitted transactions will be discarded.
Exclusion of problem 2: at this point, Platinum EP M product can be used in Server to confirm the problem. EMP can be used to monitor the operation of the system. When the Cl ient terminal crashes, monitoring the use of DML LOCK will find that due to the user's wrong operation, this user has issued a life and death lock in the database, causing the Client terminal to crash. After the process number is determined, go to the ORACLE user and use the command 'KILL-9 process number' to release the deadlock and resolve the Client end crash.
For example, when a user issues an Update, Delete command statement, and then Select, the user deadlock occurs.
In the application software development process? The Client terminal will crash due to some BUG problems in the application software. At this time, the database dictionary and database base table can be used to search, mainly based on the characteristics of the database data and database base table constraints are checked to find the problem as soon as possible, and the performance of the database has nothing to do with; You can also use EPM on the Server side to monitor the SQL statements that a 1 user is currently executing to find out what the problem is.
For example, after the user data table is added, when the application is running, DUP-VALUE-IN-INDEX and similar error messages are prompted, it is because the data fields of Primary Key of the database table are incorrectly selected, which causes the data that should not be added to the database and causes the application to crash. At this point, the problem can be solved by modifying the base table and deleting the wrong data.
Operating system: Solaris 2.5(simplified Chinese)
Disk: 4.2 GB
Memory: 256 MB
ORACLE B version: 7.3.2.1
Installation directory: /database/oracle (2GB space under /database)
Installation products: ORACLE RDBMS,SQL * NET,SQL * Plus,Pro * C,Server Manager, etc
The product is installed normally and running stably.
2. Common problems in application development and elimination
In the process of application development, the ORACLE database often encounters the following two problems:
1. You cannot close the database with Shutdown;
2. The Client terminal often crashes without any reason.
Elimination of problem 1: as long as the correct command is used to open and close the database (only Internal users have the right), problem 1 occurs because the database has uncommitted transactions. The Shutdown Abort command can be used to close the database, but all uncommitted transactions will be discarded.
Exclusion of problem 2: at this point, Platinum EP M product can be used in Server to confirm the problem. EMP can be used to monitor the operation of the system. When the Cl ient terminal crashes, monitoring the use of DML LOCK will find that due to the user's wrong operation, this user has issued a life and death lock in the database, causing the Client terminal to crash. After the process number is determined, go to the ORACLE user and use the command 'KILL-9 process number' to release the deadlock and resolve the Client end crash.
For example, when a user issues an Update, Delete command statement, and then Select, the user deadlock occurs.
In the application software development process? The Client terminal will crash due to some BUG problems in the application software. At this time, the database dictionary and database base table can be used to search, mainly based on the characteristics of the database data and database base table constraints are checked to find the problem as soon as possible, and the performance of the database has nothing to do with; You can also use EPM on the Server side to monitor the SQL statements that a 1 user is currently executing to find out what the problem is.
For example, after the user data table is added, when the application is running, DUP-VALUE-IN-INDEX and similar error messages are prompted, it is because the data fields of Primary Key of the database table are incorrectly selected, which causes the data that should not be added to the database and causes the application to crash. At this point, the problem can be solved by modifying the base table and deleting the wrong data.