The Oracle tutorial you are looking at is: common problems and exclusions for Oracle database application development. Hardware platform: SUN Ultra Enterprise 3000
Operating system: Solaris 2.5 (Simplified Chinese)
Disk: 4.2GB
Memory: 256MB
ORACLE version B: 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.
Product installation normal, stable operation.
Ii. common problems in application development and their elimination
Oracle databases often encounter the following two problems during the application development process:
1, the use of shutdown command can not close the database;
2, the client end often without cause of panic phenomenon.
Problem 1 exclusion: As long as the correct use of the command to open and close the database (only internal users have this right), issue 1 is due to the database has uncommitted transactions, at this time the database can be closed with shutdown abort command, but all uncommitted transactions will be discarded.
Exclusion of Issue 2: ⑴ can now use the Platinum EP m product to confirm the problem on the server side. The use of EMP can monitor the operation of the system, when the CL ient end occurs, monitor the use of DML lock will find that the user due to misoperation, causing the user in the database deadlock, causing the client end of the panic. After the process number is determined, to Oracle users, the ' KILL-9 process # ' command can be used to release the deadlock and resolve the client-side panic problem.
For example, when a user sends an UPDATE, delete command statement, and then selects, the user will deadlock.
⑵ in the application software development process? There are some bug problems in the application software that cause client-side crashes. The data dictionary and database base tables are used to find this. The data characteristics of database and the constraint conditions of database base table are checked to find out the problem as soon as possible, and the performance of database is not related; Of course, you can also use EPM on the server side to monitor the SQL statements that a user is currently executing. To find out where the problem lies.
For example, the User data table to add data, when running the application, prompts Dup-value-in-index and other similar error messages, is because the data base table primary key data field selection error, resulting in the data should not be added to the database, so that the application crash. You can then resolve the problem by modifying the base table and deleting the error data.
