Example-: A sales document that is created in VA01 is updated into more than 140 tables. Updates records are released from SM13 When the records are committed by the dialog process the records are displayed in SM13 with STATUS “INIT” Update Process Deactivation-: Whenever there is a problem with database like (table space overflow, archive stuck) then the updates hangs, to avoid this situation set the update to deactivate using parameter.rdisp/vb_stop_active = 0 UPDATE ERROR and ISSUES 1. Check whether right KERNEL version is deployed (if required roll back KERNEL). Update is terminated due to an error (if the error is resolved it will restart with status “AUTO”).The purpose of this article is to help you become familiar with one of Oracle9i's new features, the server parameter file--aka SPFILE.
Other SLOB-related are listed in “My SLOB IO testing index“. However, there are some things that are worth sharing with others to help out with your efforts.However, Orion has a good advantage over SLOB as it doesn’t require any installation to start testing PIO. Our goal is to see how close the results will be at least on one particular system, and if the results are different, why.—- Phase 1 Env: Oracle Linux Server release 5.8, RDBMS 184.108.40.206 (64 bit) We created SLOB DB using kindly prepared SLOB/misc/create_database_kit/README and a simple DB creation script.* edit/etc/inittab and telinit q rm -rf /etc/init.d//etc/init.d//etc/init.d//etc/init.d/rm -rf /etc/rc2.d/K96/etc/rc2.d/S96/etc/rc3.d/K96/etc/rc3.d/S96/etc/rc5.d/K96/etc/rc5.d/S96rm -rf /etc/oracle rm -rf /var/tmp/.oracle rm -rf /etc/ORCLcluster (optional) rm /etc/inittab.* srvctl add database -d DBNAME-o $ORACLE_HOME -p ' DATA_DG1/DBNAME/spfile DBNAME' srvctl add instance -d DBNAME -i INSTNAME -n ... srvctl modify instance -d DBNAME -i INSTNAME -s ASM...Total System Global Area 302747688 bytes Fixed Size 450600 bytes Variable Size 167772160 bytes Database Buffers 134217728 bytes Redo Buffers 307200 bytes Database mounted. This enables # scheduling of server # collections from the Oracle Enterprise # Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null, # every session will write to the named collection, as well as # enabling you to schedule future collections from the console. As I am going to continue writing about our ongoing IO testing efforts on this blog, I decided to provide the first post here to give readers a bit more context. We are still working on testing and analyzing the results.