Wednesday, April 10, 2013
Friday, April 05, 2013
Here are the steps:
On a replication master, you must enable binary logging and establish a unique server ID. Binary logging must be enabled on the master because the binary log is the basis for sending data changes from the master to its slaves. If binary logging is not enabled, replication will not be possible.
Each server within a replication group must be configured with a unique server ID. This ID is used to identify individual servers within the group, and must be a positive integer between 1 and (232)–1. How you organize and select the numbers is entirely up to you.
Edit your my.cnf file like this:
4. Transferring DUMPS to SLAVE with Master DB State Information:Stop the production server, and obtain its state information. Most importantly, note the File and Position values:mysql> FLUSH TABLES WITH READ LOCK;
Then unlock the master database:
5. Setting the Replication Slave Configuration
On a replication slave, you must establish a unique server ID. Edit the my.cnf like this:
After making the changes, restart the server.
6. Importing dumps into SLAVE DB:
Transfer the data (dbdump.db) file from Master and load it into the database:
Set the file information – this needs to match the values you observed on the master when you locked the tables above. In this example the filename was mysql-bin.003 and the log position was 240:
mysql> change master to
7. Start the slave:
Thats it!! Now you can create table/database and see the reflection on slave database!
Thursday, April 04, 2013
Followings are some formatted reports based upon these basic tables.
List of DATABASE Privileges:
SELECT md.host `Host`,
LIST OF GLOBAL PRIVILEGES:
List of privileges for TABLES:
List of privileges for VIEWS:
SELECT mv.host `Host`,
List of privileges for TABLE COLUMNS:
List of privileges for VIEW COLUMNS:
List of privileges for PROCEDURES:
List of privileges for FUNCTIONS:
Wednesday, April 03, 2013
- Install Oracle database 184.108.40.206 standard edition database.
- Install JDK jdk 1.6 or 1.7
- Install Repository Creation Utility (RCU) 220.127.116.11 (ofm_rcu_win_18.104.22.168.0_disk1_1of1.zip)
- Weblogic Server 10.3.6 (wls1036_generic.jar)
- Oracle Portal, Reports,Forms & Discoverer 11g and patching with 11.1.6
- Run configuration for Discoverer
At this point.....Installation of Oracle Discoverer 11g has been successfully installed.
Just one additional task is, you need to copy the database tns file, (where EUL Schema resides) needs to be copied over to Middleware Instance Directory. Ie, for my case it's
The link to use Discover would be prety much like this:
Note that, even if webcache is down, you can still access Discoverer with the 8888 port!!!