With the announcement of Oracle GoldenGate Studio at OOW this year, there has been a good bit of interest in what is can do for any Oracle GoldenGate environment. The basics of this new design tool is that it will allow the end user to quickly build out GoldenGate architectures and mappings; however, before you can build the architectures and mappings there needs to be a repository to store this information.
The Oracle GoldenGate Studio is built on the same framework that the Oracle Data Integrator is built on. With this framework, a repository database has to be created to retain all of the architectures and mappings. To do this, you use the Repository Creation Utility (RCU). Unlike ODI, the GoldenGate Studio repository can only be created in Oracle database. The RCU can be used to create the repository in any version of the Oracle Database (EE, SE, or XE).
After identifying or installing a new Oracle database for the repository; the RCU will need to be ran. The steps below will guide you through the creation of the repository needed for Oracle GoldenGate Studio.
Note: The RCU will be ran out of the Oracle GoldenGate Studio home directory.
To run the RCU, you will need to be in the Oracle GoldenGate Studio home directory. In this directory, you will need to go to oracle_common/bin as indicated below. Then execute the RCU from there.
$ cd $GGSTUDIO_HOME/oracle_common/bin
$ ./rcu &
Executing the “rcu” command, will start the RCU wizard to build the repository. The first screen of the RCU will be the welcome screen. Click Next.
Being that this is a new repository, you will want to select “Create Repository” and “System Load and Product Load” options. Click Next.
The next screen of the RCU will ask you for connection information related to the database where the repository will be built. Provide the information and click Next.
While the RCU is attempting to connect to the database, it will run a few checks to verify that the database is supported and can be used for the repository. If you get a warning, this is normal and can be ignored. Once the warning has been ignored, the prerequisites will complete. Click Ok then Next.
The next step of the RCU will allow you to select the components needed for the repository. There are only two main components needed for the repository. “Common Infrastructure Services” (selected by default) and “Oracle GoldenGate -> Repository” (selected by default). Both of these selection will have a prefix of “DEV” by default. This is something that can be changed in the “Create new prefix” box.
Note: I like changing it to GGR (GoldenGateRepository), this way I can keep different schemas in the same repository database.
Just like the database connection prerequisites, the RCU will check for all the items needed. Click OK.
The next screen will ask you for passwords that will be used with the schemas in the repository. You have the option of using a single password for all schemas or specify different passwords. Since this is mostly for testing, a single password works for my setup. Click Next.
The custom variables step will require you to create a password for the Supervisor user. Remember the Supervisior user is a layover from the ODI framework. Provide a password that you would like to use. Also notice that the “Encryption Algorithm” variable is empty. This is meant to be empty, do not place anything here. Then click Next.
Now the wizard will prompt you about information needed to create default and temp tablespaces for the schemas setup earlier in the wizard. Taking all the defaults unless there is something specific you would like to change. Click Next.
The summary page will provide you with the information on items that will be created with the RCU. Click Create and wait for the repository to be created.
Once the “create” button has been pushed, the RCU will begin building the repository.
Upon completion of the repository, the RCU will provide a Completion Summary screen with all the details of the repository build. At this point, you can close out of the RCU by clicking “close”
If you are familiar with any of the Oracle Data Integration tools, this repository wizard is very similar to other products that use a repository (example: Oracle Data Integrator). The repository is a very nice and useful with Oracle GoldenGate Studio because it will be used to keep track of projects, solutions and mapping that you will be working on.
Filed under: Golden Gate
At Oracle Open World this year, Oracle announced the release of Oracle GoldenGate Studio 12.2.1. This is a graphical design tool for Oracle GoldenGate. It will allow you to design your replication flows, map tables, and generate your parameter files based on these items.
To install Oracle GoldenGate Studio, you will need access to Java 8 (1.8) JDK. Java should be mapped to the PATH as well for easier access when installing. Additionally, you need to download the Oracle GoldenGate Studio jar files from OTN or eDelivery once it is generally available.
Note: This installation steps outlined here, were done using the latest release I had access to (beta). Some things may or may not change with the general availability release.
To begin the installation of Oracle GoldenGate Studio, you need to navigate to the directory where the jar files for installation are located and execute the java installation.
cd /media/sf_Oracle/GGATE/ggstudio/OGGS\ Latest
$ java -jar ./fmw_22.214.171.124.0_oggstudio_generic.jar
When it starts, you will be met with the Oracle Universal Installer (OUI) splash screen, which will eventually open the OUI.
After the OUI opens up, you will be on the welcome screen. On this screen, just push next to progress through the OUI.
Just like any other OUI process, you have the option to check for updates. Being that this is a new product, there are not any updates for it yet. Select the “Skip Auto Updates” and click next.
The next screen is the installation location. Provide where you would like to install Oracle GoldenGate Studio. The drop down menu on this screen, reads the OraInventory file and highlights any middle tier home that is on the machine. You cannot (and should not) install on top of an existing middleware home.
The only option for the installation is a Complete Install, which is listed on the Installation Type screen. Just click next here.
Next, the OUI will check to verify that all the prerequisites are met. If anything is not met, you will need to correct the problem. Click next.
After the verification of prerequisites have been met, the next screen that is shown is the Installation Summary screen. This screen shows you key information for where Oracle GoldenGate Studio is going to be installed and the resources that are going to be used. Click install to begin the installation.
Once the installation starts, just monitor the process until it completes. Click next or finish when it completed. If clicking finish, this will close the OUI.
With the installation complete, the final screen will provide details of the installation. Click finish when done reviewing.
Now, you can start Oracle GoldenGate Studio. In order to do this, you have to go to the $GGSTUDIO_HOME/bin/oggstudio.
Hope this gives you a sense of how easy it is to install Oracle GoldenGate Studio.
Filed under: Golden Gate
Ever since Oracle purchased GoldenGate, the biggest complaint about Oracle GoldenGate (OGG) has been around the fact that it is a command line tool. I like the command line interface of OGG, the simplicity of it and what can be done by just editing the parameter files from the command line. However, for those of you that require a graphical interface, Oracle has listened and provided a new tool. This tool is Oracle GoldenGate Studio!
This year at Oracle Open World 2015, Oracle announced Oracle GoldenGate Studio Release 1 (12.2.1). This is Oracle’s first step into bringing Oracle GoldenGate into the GUI environment. Studio is a design tool that complements the monitoring tools that Oracle provides for GoldenGate.
As a design tool, you can do a range of things now. A few of the thing are as follows:
- Build out a wide range of Oracle GoldenGate architectures
- Synced parameter files to systems where Oracle GoldenGate is running or dump the files to a directory for later installation
- Export/Import GoldenGate Solutions
- Define mappings in either local or global settings
When you first start Oracle GoldenGate Studio, anyone who has worked with Oracle Data Integrator will notice some similarities. This is because the initial framework for Oracle GoldenGate Studio is built around the ODI framework. This is good because if provides a familiar looking interface for the end user.
Just like ODI, Oracle GoldenGate Studio uses a repository. This repository can be the same repository as many other Oracle products. In my environment, I’ve got Oracle GoldenGate Studio running against a 126.96.36.199 database. The repository is used to keep track of all the mappings needed to keep track of the architectures that is designed within the studio.
Overall, my initial thoughts on this product are:
- For a first release, it is good but has some limited functionality
- I like the interface and it helps to make quick work of designing a flow; however, initially there will be a learning curve for most GoldenGate Admins (no more Visio diagrams need to track)
- Not thrilled with having another repository to keep up with; nice that is can be combined into other repositories if needed, just need to make sure schema names do not overwrite
With this tool being announced at Oracle Open World, expect some great blogs about this tool being road tested as well. In the mean time, once it becomes available (after OOW15) give it a try. It will make your life a bit easier.
Filed under: Golden Gate
In 2014, myself, Danny Bryant and Stewart Bryson, from the Atlanta area were added to the board of directors for the Georgia Oracle User Group (GaOUG). With us being added to the Board of Directors, we initatied a rebranding of the user group from GOUSER to GaOUG in Feburary 2015, with much success. Then followed that event up with two quarterly events in April and July 2015, which proved to be an even bigger sucess and we continue to build on each success due to people we have been able to attract for quarterly events. After the success of our quarterly events, the board of directors established a goal of bringing the best speakers, locally, nationally and internationally, to the Atlanta area for a 1 day conference in 2016. So, I’m here to promote the conference and to hopefully convence you to submit an abstract to this new event on the conference circuit.Little Background:
When I first moved to the Atlanta area (2001), I didn’t know anything about Atlanta much less the Oracle community. I joined GOUSER around 2006 with little going on in the community (story for another time). It wasn’t until 2012, when I first ventured out onto the conference stage at Oracle Open World 2012. For my first conference, it was nerve racking to say the least; however, I was introduced to many great people that year and my career, personal and professional networks, and friendships have benefited from that experiance. These are just some of the reasons why I keep submitting annually for a wide range of conferences and why I’m helping to bring this conference to Atlanta.Conference:
The aim of GaOUG Tech Day 2016 conference is to start small and grow into the best regional Oracle User Group conference in the Southest! This can only be achived with the help of great speakers (new and existing) from the Oracle Community! With that being said, our call for papers is currently open (submit here).
GaOUG Tech Day 2016 will have three categories for abstract submissions. These include Database & Development, Middleware and Applications. These categories cover a wide range of technologies form the Oracle stack plus many others.Submitting an Abstract:
Before you submit your abstracts, there are a few reminders that you should be aware of that make a great abstract:
- Take the time to make a great abstract title and fill out the abstract and summary completely!
- Run it through spelling and grammar check. If you submit a “sloppy” abstract with misspellings and errors in grammar, how can we know that you’ll take the time to ensure that the presentation will be performed professionally and technically accurate?
- List a few take-aways the attendee will leave with. What is the value that will be gained by attending your session?
- Fill out your speaker biography. We like to know a bit about you and why you are important to have presenting at the conference.
- No marketing! Keep your session technical. Our conference is a technical conference and nothing irks our attendees like marketing! If they like what you are teaching, they’ll search out your company and/or product- trust me!
(Tips were provided by DBAKevlar, thanks Kellyn!)First/Local Time Speakers:
Finally, if you are submitting an abstract and you are a first time or local speaker; do not hesitate to reach out to the board and ask for guidance and/or mentoring. The board of directors has the experience to assist you in your submissions and selections. We are looking forward to and wanting to hear from new speakers in the community and help build your confidence in the speaking arena.
Submit your abstract today! Deadline for submissions is November 2nd, 2015!
Filed under: GaOUG, General
A few months ago, I heard that Oracle was releasing a plug-in for the Oracle Database Appliance (ODA (Oh Dah). At first I couldn’t find anything on this plug-in, then I was able to find it in the Self-Update for Plug-ins (Extensibility -> Self Update -> Plug-ins).
After finding the plug-in, it needed to be deployed to the Oracle Management Server (OMS). Once deployed, it can be used to monitor the ODA; however, this plug-in is different from plug-ins like the Exadata, where you have a wizard to configure monitoring of the hardware associated with the engineered system. In order to use this plug-in, the two servers in the ODA have to have the EM agents installed on them. Here is a list of articles, by some great guys plus myself, that relate to installing agents in EM12C (if you don’t know how to do that already).
Once the agents are installed, then the plug-in has to be added to the agent. This is achived by pushing the plug-in from the same screen where the plug-in was deployed to the OMS. Only this time, it is deployed to the newly added agents (Extensibility -> Plug-Ins -> Deploy On -> Management Agent)
Once the plug-in is deployed to the new targets for the ODA servers; then the ODA can be added to OEM.
To add the ODA with the plug-in, it can now be done through the Add Targets Manually process. This step is a wizard that walks through adding the ODA; is done through the Add Targets Using Guided Process.
When starting the discovery, OEM will provide you a Discover Now button which initiates the wizard for discovering the ODA componenets such as ILOM and the servers.
When the wizard starts, it asks for an agent URL. This is the agent installed on the first node of the ODA. Then provide the host root login that is stored in Named Credentials or a new login.
The next step of the wizard, will provide a list of all the discovered targets in the ODA.
On the credential screen, the wizard asks for the root password for both the host and the ILOM. If the passwords are the same across the ODA there is a n option to use the password for both items being granted.
The Tag Cloud step is interesting. You really don’t have to put anything here; however, you can tag the ODA to help identify what is being added. There is a Create Tag button at the bottom if you want to create a tag. (I didn’t create one so I didn’t include a picture in this post).
Finally, the review step shows what is going to be added to OEM as the ODA. Once the targets have been promoted successfully, you will see a green flag in the Discovery Stataus block. At this point the ODA has been added to OEM.
Now that the ODA has been added to OEM, it can be viewed from Targets -> All Targets -> Target Type -> Engineered Systems -> Oracle Database Appliance System. From here, OEM takes you to the home page for the ODA.
From the ODA home page, it provides an overview of all the item going on with the ODA. Click around and have some fun reviewing what is happening with the ODA being monitored.
Filed under: OEM
How do you monitor an ZFS Storage Appliance with Oracle Enterprise Manager 12c? This is a question that has been asked a few times and I needed to solve this issue. You hear a lot about the em agents and that they need to be used to monitor many different targets. Let’s just say, that is not the case when wanting to monitor a ZFS Storage Appliance.
In order to monitor a ZFS Storage Appliance, there are a few things that have to be setup first. After configuring your ZFS the way you want it, you have to create an oracle_agent user and role within the ZFS.
To create a user on the ZFS, you need to login to the ZFS and then go to Maintenance -> Workflows and click the “Edit” option next to Configure for Oracle Enterprise Manager Monitoring.
The workflow will create a user and role named “oracle_agent” when complete. Click the OK button to allow the workflow to perform the actions needed. (It may take a few minutes to pop-up the status window)
After clicking the OK button, the ZFS will configure a worksheet that is used to monitor the ZFS from OEM. At this point, the ZFS is ready to be monitored from OEM.
In order to set up the ZFS within OEM, it needs to be added manually. This is done by using the Setup -> Add Target -> Add Targets Manually. Once on the Add Targets Manually page, the ZFS needs to be added by using the Add Targets Declaratively by Specifying Target Monitoring Properties. On this page, select the Target Type for the ZFS and the monitoring agents should be the EM Agent for the OMS.
Note: The monitoring agent, can be any agent that you want to monitor the ZFS with. The agent will act as a proxy to the ZFS.
The next screen, within OEM, will ask you for the specific information needed to add the ZFS to be monitored. The target name can be anything you would like to call the ZFS. Username and Password are what you configured when setting up the worksheet (oracle_agent). The management port (215) is the default port. Lastly, the IP address or DNS name of the ZFS to be monitored.
After clicking OK, the ZFS will be added to OEM. To verify this, the ZFS can be found under Targets -> All Targets -> Oracle ZFS Storage Appliance
Finally, the ZFS can be viewed and monitored from within OEM.
Keep in mind that the metrics being collected will update over time. The image above is captured from a newly discovered ZFS and has not had time to populate.
Filed under: OEM
I’ve been doing some Enterprise Manager installs a bit more lately. At the same time, I’ve been working on Data Integration items such as GoldenGate and ODI. What these products have in common are that they require an Oracle Database for a repository. Needless to say I’ve been installing a lot of 188.8.131.52 databases in test and production environments. The one thing that has been consistent is the issue I keep seeing with PERL that is packaged with the Grid Infrastructure and/or Database.
Tip: This may not be happening to everyone and I may have a bad set of binaries. In discussing this with a co-worker, the md5sum sets were the same for my set of binaries as they were for his. So I couldn’t say if this issue was bad binaries or something else.
As I was doing installs of Grid Infrastructure or Database on Oracle Enterprise Linux 6.6, I would get the following issue when trying to run the root.sh scripts from either the OUI or from the command line.
[root@rac1 grid]./root.sh Performing root user operation.</p> <p>The following environment variables are set as: <br> ORACLE_OWNER=oracle <br> ORACLE_HOME=/u01/app/grid/12.1.0/grid <br> Copying dbhome to /usr/local/bin... <br> Copying oraenv to /usr/local/bin... <br> Copying coraenv to/usr/local/bin ...</p> <p>Entries will be added to the /etc/oratab file as needed by <br>Database Configuration Assistant when a database is created <br>Finished running generic part of root script.<br>Now product-specific root actions will be performed.<br><strong>/u01/app/grid/12.1.0/grid/crs/config/rootconfig.sh: line 131: 20862 Segmentation fault (core dumped) $ROOTSCRIPT $ROOTSCRIPT_ARGS</strong><strong>The command '/u01/app/grid/12.1.0/grid/perl/bin/perl -I/u01/app/grid/12.1.0/grid/perl/lib -I/u01/app/grid/12.1.0/grid/crs/install /u01/app/grid/12.1.0/grid/crs/install/rootcrs.pl ' execution failed</strong>
You will notice that the execution failed with a “Segmentation fault”. In looking at the command, I noticed that this is running perl from the $ORACLE_HOME/perl/bin directory. When I did a “which perl”, the perl that the operating system is using is coming from /usr/bin/perl. This is not the correct one being used by the root.sh script. Also if I did a “perl -v” from the command line it returns that the version of perl is 5.10.
Now that it is established that the operating system installed perl is fine, I took a look at the perl in $ORACLE_HOME/perl/bin. When I navigated to the $ORACLE_HOME/perl/bin directory and executed “perl -v”; I was met with the “Segmentation fault” issue. Knowing that the problem is within the Oracle binaries; how can this be resolved?
To resolve this “Segmentation fault” issue, I had to recompile the perl binaries that Oracle uses in the $ORACLE_HOME path. To do this, I had to download and recompile the perl binaries in the $ORACLE_HOME directories.
<br>$cd ~/Downloads <br>$wget http://www.cpan.org/src/5.0/perl-5.14.4.tar.gz <br>$tar -xzf perl-5.14.4.tar.gz <br>$cd perl-5.14.4 <br>$./Configure -des -Dprefix=$GI_HOME/perl <br>$make <br>$make test <br>$make install <br>
With the binaries recompiled, I was now able to run a “perl -v” from the $ORACLE_HOME and get a successful result set.
<br>[oracle@rac1 ~] cd /u01/app/grid/184.108.40.206/grid <br>[oracle@rac1 grid] cd perl/bin <br>[oracle@rac1 bin]./perl -v </p> <p>This is perl 5, version 14,subversion 4 (v5.14.4) built for x86_64-linux </p> <p>Copyright 1987-2013,Larry Wall </p><p>Perl may be copied only under the terms of either the Artistic License or the <br>GNU General Public License, which may be found in the Perl 5 source kit.</p><p>Complete documentation for Perl, including FAQ lists, should be found on <br>this system using "man perl" or "perldoc perl". If you have access to the <br>Internet, point your browser at http://www.perl.org/, the Perl Home Page. <br>
This process can be done if the OUI is running and the step that hung can be retried. If you closed out the OUI, then the root.sh scripts will run successfully now from the $ORACLE_HOME directories.
Filed under: Database, General