In this tutorial you will learn how to install oracle 11g on windows x86_64. ![]() Two major prerequisites for installing Oracle Enterprise Manager (OEM) are having an existing, certified Oracle Database and an installation of Oracle WebLogic Server. Steve Callan shows you the steps performed for database preparation and for installation of Oracle WebLogic Server. Two major prerequisites for installing Oracle Enterprise Manager (OEM) are having an existing, certified Oracle Database and an installation of Oracle WebLogic Server. For the purposes of this article, let's assume you already have an existing database (11g) with Database Control configured. The word 'keygen' means a small program that can generate a cd key, activation number, license code, serial number, or registration number for a piece of software. Kumpulan serial number idm. Take the FileFixation now for more detailed information! That's pretty much what you get anyway as a result of a normal or regular installation of Oracle on a server (including your own PC or laptop). This article looks at the steps performed for database preparation and for installation of Oracle WebLogic Server. Database preparation All steps involve create or install, with the exception of one component on the existing Oracle database. Given that Database Control was configured, then its repository must be deconfigured and the existing SYSMAN schema must be dropped. The installation and configuration of OEM creates its own SYSMAN user. Along with the new SYSMAN (and SYSMAN_MDS) user comes a MGMT tablespace with several data files. Installation of OEM, as in what you would do in a workplace, you?d definitely want to comply with all requirements listed in the Oracle Enterprise Manager Grid Control Basic Installation Guide. The table below is a collection of various links, patch numbers and support notes from My Oracle Support. Master Note for installing OEM MOSC note 1067438.1 Oracle Enterprise Manager OEM page at OTN List of certified browsers and operating system requirements MOSC support note 412431.1 JDK Java page at OTN WebLogic Server page at OTN Oracle WebLogic Server WebLogic Server page at OTN WLS patches (WDJ7) MOSC note 1072763.1 (If upgrading) MOSC note 1073166.1 Deconfig of Database Control MOSC note 375946.1 (in case the removal process hangs) Given that we?re starting with an already installed/created database using Database Control, let's start with getting the database side of things ready to go. The version of OEM is 11.1.0.1, and it will be installed on a Windows 2003 SP2/R2 server, and will use an Oracle 11.2.0.1 database. ![]() The certification checker note (412431.1) shows this to be a valid combination. Deconfigure the existing Database Control This is simply a matter of running the emca command using (from the docs): $/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD -SYSMAN_PWD For the Windows 2003 environment/path/etc setup, the following can be used: C: Documents and Settings Administrator>echo%oracle_sid% ORCL2 C: Documents and Settings Administrator>emca -deconfig dbcontrol db -repos drop STARTED EMCA at Nov 11, 2015 9:52:11 AM EM Configuration Assistant, Version 11.2.0.0.2 Production Copyright (c) 2003, 2005, Oracle. All rights reserved. Enter the following information: Database SID: orcl2 Listener port number: 1526 Password for SYS user: Password for SYSMAN user: Do you wish to continue? [yes(Y)/no(N)]: y Nov 11, 2015 9:54:16 AM oracle.sysman.emcp.EMConfig perform INFO: This operation is being logged at C: app oracle cfgtoollogs emca orcl2 emca.log. Nov 11, 2015 9:54:21 AM oracle.sysman.emcp.EMReposConfig invoke INFO: Dropping the EM repository (this may take a while). Nov 11, 2015 9:57:35 AM oracle.sysman.emcp.EMReposConfig invoke INFO: Repository successfully dropped Enterprise Manager configuration completed successfully FINISHED EMCA at Nov 11, 2015 9:57:42 AM Drop the SYSMAN (and SYSMAN_MDS) schema More than likely, you will not have the SYSMAN_MDS schema, so this is just a matter of dropping the SYSMAN schema. Under Windows, take advantage of a supplied script/batch file named RepManager.bat, found in $ORACLE_HOME sysman admin emdrep bin. The SYSMAN schema may already be dropped, and to check this ahead of time, look for SYSMAN in DBA_USERS. Running the RepManager.bat file is benign if SYSMAN is no longer present. With respect to running the RepManager batch file, you cannot use the example shown in the OEM installation guide. The batch file calls a Perl script, which in turn is looking for a host of other environment variables. Hunting down the usage details (either within the called Perl script or Oracle documentation), a format such as this will work (run within the bin folder at the command prompt): RepManager win2003 1526 orcl2 -sys_password oracle -action drop The format is (all on one line, line return shown here for formatting): RepManager -sys_password -action drop To avoid some other screen output/feedback, you can set some environment variables in the commenenv.bat file found in the bin folder under ORACLE_HOME.
0 Comments
Leave a Reply. |