Posts

Showing posts from July, 2018

Swingbench Short cookbook commands

Image
In this example we are using Swingbench 2.6 with Order Entry stress test - using a configuration file (SOE_Server_Side_V2.xml) Connection String: The connection will always be defined to pluggable database (not CDB) - if installed. //hostname/service_name valid for driver type: Oracle oci Driver & Oracle jdbc Driver ( oewizard , sbutil use only this option) . Make sure the service name is recognized by the listener ( lsnrctl services | grep Service ) Tnsnames alias valid only for driver type: Oracle oci Driver – requires Oracle 12.2 client Creating the schema: cd swingbench/bin $ ./oewizard -dbap change_on_install -ts SOE -nopart -u soe -p soe -cl -df +DATA -create -scale 1 -cs //db_server/db_service Running: If you need to use Connection Pooling : Change the driver type to " Oracle oci Driver" Change the format of the connection string to tns alias For further needed changes, look at: Application Continuity in Oracle Database 12c (12.1.0.2) charben

Steps To Shutdown / Startup The Exadata

Image
ShutDown Log in to the first database server as root. Change to the OneCommand directory # cd /opt/oracle.SupportTools/onecommand Note whether the Grid Infrastructure is currently enabled for autostart, so that this state can be restored later: # dcli -g dbs_group -l root /u01/app/12.1.0.2/grid/bin/crsctl config crs Disable the Grid Infrastructure for autostart on the database servers if the previous step indicated it is currently enabled for autostart. # dcli -g dbs_group -l root /u01/app/12.1.0.2/grid/bin/crsctl disable crs Note: This is step is [Optional] and it can required during maintenance operation like “firmware patches” which requires to reboot the Compute Node several times. Stop the Grid Infrastructure stack on the database servers (compute nodes): # dcli -g dbs_group -l root "/u01/app/12.1.0.2/grid/bin/crsctl stop crs" Verify that the Grid Infrastructure stack has shutdown successfully on the database servers. The following command should show no output if

Install Oracle Internet Directory (OID) in Standalone mode

Image
Oracle Internet Directory (OID) is an LDAP server which uses an Oracle database as a datastore. Client machines can use the OID for all TNS lookups. With OID. Once all client machines are configured correctly any modifications to the TNS lookups can be done from a central location reducing the amount of client machine administration. This guide is about installing and using Oracle Internet Directory in Standalone mode, no need for Oracle Fusion Middleware Infrastructure. Step-by-step guide Download Oracle Internet Directory (Part of identity management) from http://www.oracle.com/technetwork/middleware/id-mgmt/downloads/index.html Install OID, follow instructions: https://docs.oracle.com/en/middleware/lifecycle/12.2.1.3/inoim/installing-product-software.html#GUID-5D47117E-3983-4BED-BADB-CB7DDD63DB34 Starting the Installation Program: ./fmw_12.2.1.3.0_oid_linux64.bin Configure the Domain: $ORACLE_HOME/oracle_common/common/bin/config.sh Start the Servers for Standal