Steps for Changing the SYSMAN Password in 10.2.0.5 and 11.1 Grid Control
When using 10.2.0.5 or 11.1 OMS, all the above steps can be performed by executing a single command:
Example of output for OMS 10.2.0.5 running on Windows:
1. The above command
- will prompt you for the current password and the new password.
- will modify the sysman password in the repository database, in the emoms.properties configuration file / WLS Credential store and the monitoring credentials for the ‘OMS and Repository’ target.
- will ask you to bounce the OMS once the command is completed successfully
- for 11G, the command will modify the password for sysman and sysman_mds users in the repository database, modify the password in the credential store and change the monitoring credentials for the ‘OMS and Repository’ target.
2. The ‘-change_in_db’ parameter is optional and is used to change the SYSMAN password in the repository database.
- If the sysman password is manually modified in the repository database, this option need not be specified.
- When this parameter is specified, the command will prompt for the current sysman password.
- If the current sysman password is lost / unknown then:
a) Log in to your Repository database as SYS and run:
where newpassword is the new password you want for SYSMAN.
b) From a command prompt run:
./emctl config oms -change_repos_pwd
Provide newpassword when prompted.
3. If using multiple OMS, then execute the above command on one of the OMS.
On the Additional OMS, execute:
Installation and Configuration EPM 11
EPM Oracle Home
An Oracle home contains installed files necessary to host a specific product, and resides within the directory structure of the Middleware home. The EPM Oracle home contains files for EPM System products.
The default EPM Oracle home location is MIDDLEWARE_HOME/EPMSystem11R1. In addition, common internal components used by the producs are installed in EPM Oracle home. Choose the location carefully to ensure that the location has enough disk space for all of the products you are installing on that machine. You CANNOT change the location at a later time.
The EPM Oracle home location is defined in the system environment called EPM_ORACLE_HOME. The EPM Oracle home directory structure must be the same on each machine. Additionally, during configuration some products deploy components to MIDDLEWARE_HOME/user_projects/epmsystem1. Deplopyed components include the following:
- Data and applications
- Deployed Web applications
- Log files
Web applications are deployed in MIDDLEWARE_HOME/user_projects/domains/domainName.
Essbase and Oracle Process Manager and Notification (OPMN) Server
Oracle Process Manager and Notification server (OPMN) enables you to monitor and control the Essbase Agent process. You add Essbase Agent information to opmn.xml to enable OPMN to start, stop and restart the agent using the OPMN command line interface. OPMN can automatically restart the Essbase Agent when it becomes unresponsible, terminates unexpectedly, or becomes unreachable as determined by ping and notification operations.
If you configured more than one instance of Essbase Server on a single machine, each instance has its own OPMN, its own start scripts, and its own log files. You must update each instance’s copy of opmn.xml so that each OPMN has unique ports for communication.
See Appendix H, “OPMN Service Failover for Essbase Server” and Oracle Essbase Database Administrator’s Guide, “Managing Essbase Using OPMN“.
Downloading the Installation Files
Download the installation files from “Oracle Enterprise Performance Management System” page of the Oracle E-Delivery (http://edelivery.oracle.com) site into /download_location. Note that some files are posted by platform; make sure to download the files for the platform you will be using.
Review the Media Pack Readme on the Oracle E-Delivery web site to see which ZIP files to download depending on the products you own and the platform you are deploying those products on.
Unzip the EPM downloaded files into /download_location, if you are prompted with a message that any files may already exist be sure to click “Yes” to overwite the existing file(s). Be sure to unzip the files into the same exact directory /download_files. The assemblies are automatically unzipped into an /assemblies directory under /download_files. For information about specific assemblies related to the various product components see the section “Component Installation By Tier and Installation Assemblies” on page 29 of the “Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide RELEASE 11.1.2“. NOTE: Make sure to check that you are using the latest up to date Installation Guide, the one I am using for my installation during the month of December 2010 contains the notation “Updated: November 2010″ and I believe is the 1st update since this release shipped.
NOTE: Even though you need the EPM-Foundation Services ZIP files on each machine in the environment, install Foundation Servers Web applications on only one machine. On the machine you which you plan to administer the WebLogic Server, you must install all Web applications for all applications you plan to deploy on any machine in the environment. For more information see “Installing EPM System Products in a Distributed Environment” on page 89.
The /assemblies directory should include a subdirectory for each product that you want to install on the machine. Ensure that /assemblies directory looks as follows:
The following post is from: http://www.sysprobs.com/windows-7-network-slow
Often I hear from Apple users that when they map to Window share points performance is bad when they navigate from one directory to another, open files, etc. Simply refreshing a directory listing can hang and eventually result in a disconnection. I’ve posted some blog postings addressing this specific topic.
Windows 7 got some improved features than Vista including speed of network. Sometimes you may notice the network slowness compare to XP due to more advanced features and requirements. These 6 easy steps to help solving Windows 7 network slow problem by disabling some features.
Network is a major factor in computing. Windows 7 computers will be slow in accessing shares on old MS Windows servers and non MS Operating systems including Sun and Linux. Accessing data and transferring data over network are still problem in this case. Resolving DNS requests internally (LAN or WAN) and externally (Internet) also could be slow in Windows 7. The following methods I’m listing out is worked for me to speed up Windows 7 networking with NT,2003 and Sun servers.
How to Fix Windows 7 network slow problem?
1) Disable Autotuning
Disabling autotuning will help much on DNS lookup and network discovery. It improves the data transfer speed also over the network. Disabling autotuning in windows 7 is very similar toWindows vista method. Read more here about disabling autotuning in windows vista.
Startas administrator, and follow the commands as shown in below example.
2) Remove RDC ( Remote Differential Compression)
This feature introduced with Windows Vista to transfer data over network in compressed format. The same RDC feature continued in Windows 7 also. Since most of the old operating systems came before vista do not support this RDC feature, it slows down network data transfer in windows 7. You can remove this RDC (Remote Differential Compression) in windows 7 by visiting control panel and programs and features. Click on ‘Turn Windows features on or off’, as shown below.
Remove RDC ( Remote Differential Compression) in Vista
3) Remove IPv6 from network properties.
If your internal or external networks do not require IPv6 protocol, better remove it under network connection properties. Keeping IPv6 in your computer sometimes slows down network by trying to register IPv6 addresses, or trying to get IPv6 address, or trying to resolve IPv6. Better remove it if it’s not required.
Remove IPv6 in Windows Vista
4) Clear DNS Cache
You can remove any DNS cache from computer, so next time DNS request will be solved by updated DNS server. This will avoid your computer to try broken or changed DNS records from cache. To clear DNS cache, open command prompt as administrator and type ipconfig /flushdns
Ceaer DNS Cache in Vista
5) Disable Wireless Network and any additional (including Virtual adapters) network adapters.
If you will not be using wireless network or it’s your secondary network, I recommend you to disable wireless network in windows 7 under network connection. If it’s enabled, windows 7 computer will be trying to connect available wireless network around you, and trying to login though its network. Loading your profiles and start up programs will be slow while booting because of this.
6) Modifying Link Speed & Duplex Value in Network adapter Properties.
This step also helps sometimes when you face problem with windows 7 network slow. I can’t say which option will work better, because it depends on your physical network setup (network adapter, cable type, LAN speed and network switch). By default it is set for Auto Negotiation. But you can play around with Value options and find out which is working better for your computer and network.
I’m sure above steps will help to solve windows 7 network slow. Feel free to suggest any additional steps you did to solve windows 7 network slow, or problems you face to fix it.
- When you go to the Connect to Server dialog, you may browse the names of computers that are on your local subnet.
- You can connect to a server via its IP address or DNS name. If it is required or more convenient in your environment, you may also use other valid URL formats, such as:
- The name of the “share” (the shared disk, volume, or directory) must be specified. You will not be prompted for it.
- You cannot type spaces as part of the share name when connecting. In place of any space in the share name, type: %20 .
- When troubleshooting a connection issue, you can ping the IP address of the Windows PC using the Mac OS X Network Utility application (in the Utilities folder). A successful ping verifies a TCP/IP connection between the two computers. This is an important first troubleshooting step when there’s no response or a timeout for a connection attempt, since SMB connections involving a Mac require TCP/IP. However, a successful ping does not mean the SMB service is also working or available.
- Check Microsoft support resources for information about setting up file sharing on your Microsoft Windows-based computer. These may include Help files installed on your PC or the Microsoft online Knowledge Base. For example, see this article for Windows XP information: How to use the Simple File Sharing feature to share files in Windows XP.
- When troubleshooting an SMB connection issue, use Console, which is located in the Utilities folder. These Console logs may help advanced users identify an issue: private/var/log/samba, private/var/log/kernel.log, system.log . Note that some log files only appear when logged into Mac OS X with an administrator acccount.
- If you are connecting to Windows XP, make sure that the Internet Connection Firewall settings are not interfering with your connection. SMB uses ports 137, 138, 139, and 445. These ports should be open on the Windows XP computer. This may require “Advanced” configuration of the XP firewall.
- If you are connecting to a Windows SMB resource, check to see if the firewall is blocking TCP ports 137, 138, 139 and 445. After trying the above steps, you may perform advanced troubleshooting by inspecting log entries in the Event Log of the Windows SMB resource (if you have access to it), and/or the Mac OS X computer’s relevant logs in the Console application. If those steps do not help identify the issue, or you do not want to perform advanced troubleshooting, than you should contact your network administrator. It may be necessary to contact your network administrator in some situations in order to grant access to your Mac from the SMB resource, or its host network configuration.
- Mac OS X uses SMB only over the TCP/IP protocol, not the NetBEUI protocol.
1) Turn off Sync Services in Preferences.
2) Export your contacts as .olm file. Under File > Export select just contact to export. In the export process select to delete after exporting. If there is a problem you can always import this file.
3) Turn on Sync Services and let the good Apple Address Book data sync back to Outlook.
4) Check YOUR name and make sure there is only ONE “me” contact.
Apple Address Book does have a delete duplicates. I didn’t mention it before because the Address Book didn’t have dupes to delete. I believe it’s under Card in the Menu bar.
We are seeing new issues with Outlook and having to learn ways to fix. Normally, when Entourage had dupes there were also duplicates in the Address Book, phone and MobleMe. Now we are seeing dupes only in Outlook which indicates something new with the sync issue.
I can’t stress enough how important backups of your Outlook data is in case of failure. I suggest copies of your entire Identity and exporting data as .olm file(s).
When you import the .olm file in Outlook it will place the imported contacts under the archive file. You can move them to the Address Book you want to use. Afterwards, delete the empty archive folders.
There are some shortcuts that are old but for whatever reason no one remembers them or is aware of them.
An example of one of these ancient shortcuts is Command Click with you mouse pointer on top of an item in your dock. Executing this shortcut will open up the location of the file or application in the Finder or Path Finder.
This comes into play on those occasions where you want to edit or move an application or file, but you don’t know where it is located at or you don’t want to have to search for it. Stacks have that “show in Finder button” but it can become annoying to search for items when you have a stack with a large number of files in it. This can be a very useful shortcut in those instances.