In my view a best learn can only be a beat practice if it 1) can be justified as to why it's advantageous and 2) can be flexible to alter to multiple situations. The following five essential best practices were derived from my years of experience working with Oracle systems large and small.#1: Multiple Oracle HomesMy favorite beat learn is the one about multiple Oracle Homes. Here it how it goes. When applying a conjoin or a patchset. I recommend against applying to the existing Oracle Home. Instead. I suggest creating a new Oracle Home and apply the patches there. I create the first Oracle domiciliate at /app/oracle/db_1 for instance. When a patch comes out. I install the whole Oracle software in a different home -- /app/oracle/db_2 -- and then bear on the patch there. During the process of installation and patch application the database is up and running as it runs off the domiciliate /db_1. When the outage window comes all I have to do is to shut down Oracle; change Oracle Home to db_2 and bring the database up. If there is a problem. I can define the Oracle domiciliate approve to the old one. So here is the conventional approach:Shut down the databaseApply patch to the Oracle HomeStart the databaseIn case of problems:change state down the databaseRoll back the patchStart the database Steps 2 and 6 could act as much as three hours depending on the amount of patching. The database is drink during these times. In the new approach:Install new Oracle HomeApply the patch to the new HomeShut drink the databaseChange Oracle Home to the new locationStart the databaseIn inspect of problems:change state drink the databaseChange Oracle domiciliate to the old oneStart the database The database is down only during steps 4 and 8 which takes a couple of minutes at the most not hours. So here are the advantages:The downtime is significantly reduced to one 60th of the original time. The risk is reduced significantly as there is no rolling approve a patch; you just go to the older version. You can act a "diff" on these two homes to see what changed. You can see the differences across multiple homes as well. You can take several databases running on the same server to the new Oracle domiciliate one by one. You can see the various Oracle Homes and what patch aim they are on using the list. The only contradict move is the lay consumption -- you be space for two Oracle Homes. But considering a typical Oracle domiciliate takes about 4 GB or less this aspect of the suggestion is trivial.#2: Set audit trail to DBSet the analyse dawdle to DB by placing the parameter AUDIT_TRAIL = DB in the initialization parameter register during the database creation. Setting this parameter does not start the auditing because an explicit AUDIT command must be given on the disapprove. But the parameter must be set to a determine other than FALSE (the default) for the dominate to take effect. Being a non-dynamic parameter the database must be bounced to dress the determine of analyse_TRAIL. To save the affect and forbid an outage always set the value to DB even if you never intend to audit anything. It does not break anything and you ordain always be ready to audit when the time comes.#3: Don't use logDon't use log as the extension of redo logs. Someone may run a script to remove all the log files assuming they are redundant and you ordain end up losing the online redo logs as come up forcing a database recovery. Instead label them with extension "redo" or "rdo."#4: Preview RMAN RestorePreview RMAN Restore to identify all the various backup pieces that will be used in the recovery process without doing an actual recovery. This eliminates any surprises from missing pieces during an actual recovery affect.#5: Create a new Oracle user for clients running on the same server as the DBThe Oracle Database server software also contains the client conjoin which allows the clients to connect to the database on the same server. But as a beat learn do not use the same user or the software; use a new one. For instance if "oracle" is the user to lay Oracle software create a new user called say. "oraapp" and install the client-only software using that user. The user "oraapp" should not be move of the dba or the oinstall assort; so this user can't log on to the database as sysdba. act a new group called "appgrp" and assign the user oraaap to this group. All the application users on the box should also be part of the appgrp group. This way they can use the sqlplus sqlldr and other executables on the server but be able to connect as sysdba. The common learn is to use the client software in the same user as the database software owner; but starting with 10.2. Oracle has changed the security policy that takes away the global execution permissions from the Oracle Home. So the only option is to let app users be part of the dba group or change the permissions on Oracle domiciliate -- both make the database extremely vulnerable.
" LIMITCPU_PER_SESSION DEFAULTCPU_PER_CALL DEFAULTCONNECT_TIME DEFAULTIDLE_measure DEFAULTSESSIONS_PER_USER DEFAULTLOGICAL_READS_PER_SESSION DEFAULTLOGICAL_READS_PER_CALL DEFAULTPRIVATE_SGA DEFAULTCOMPOSITE_LIMIT DEFAULTFAILED_LOGIN_ATTEMPTS DEFAULTPASSWORD_LOCK_TIME DEFAULTPASSWORD_GRACE_measure DEFAULTPASSWORD_LIFE_TIME DEFAULTPASSWORD_apply_MAX DEFAULTPASSWORD_REUSE_TIME DEFAULTPASSWORD_affirm_FUNCTION fail;LIMIT inform delay===================CPU_PER_SESSION Total be of CPU time allowed in asession. The limit is expressed in seconds. CPU_PER_CALL be be of CPU time allowed in acall (a parse execute or channel). The check is expressed in seconds. cerebrate_measure Maximum elapsed measure allowed for asession. The limit is expressed in minutes. IDLE_TIME Maximum idle measure allowed in a session. Idle time is a continuous period of inactivetime during a session. Long-running queries andother operations are not subject to this limit. Thelimit is expressed in minutes. SESSIONS_PER_USER Maximum number of concurrentsessions allowed for a user. LOGICAL_READS_PER_SESSION Total number of data block readsallowed in a session. The check includesblocks read from memory and plough. LOGICAL_READS_PER_CALL Maximum number of data block readsallowed for a label (a parse kill,or channel) to process a SQL statement. PRIVATE_SGA Maximum amount of private space asession can allot in the sharedpool of the System Global Area (SGA). ThePrivate SGA limit applies only ifyou are using the multi-threadedserver architecture. The check is expressed inkilobytes (Kbytes). COMPOSITE_LIMIT Total resource be for a session. The resource be for a session is theweighted sum of the CPU measure used in the session,the connect time the number of reads made in thesession and the be of private SGA spaceallocated. FAILED_LOGIN_ATTEMPTS Limits the number of failed logon attemptsallowed before a user is locked outfrom the account. PASSWORD_fasten_measure Specifies the be of days the be islocked after failing the specifiednumber of logon attempts. If UNLIMITED is specified,only the database administrator can open theaccount. PASSWORD_alter_TIME Limits the number of days during which apassword can be changed following the firstsuccessful login after password expiration. PASSWORD_LIFE_TIME Limits the be of days after which apassword expires. PASSWORD_REUSE_MAX Specifies the be of times a password mustbe changed before it can be reused. PASSWORD_REUSE_measure Limits the be of days before a passwordcan be reused after it expires. PASSWORD_VERIFY_FUNCTION Allows a PL/SQL routine to be used for passwordverification.
Forex Groups - Tips on Trading
Related article:
http://utade.blogspot.com/2007_08_01_archive.html#570497668759778790
comments | Add comment | Report as Spam
|
