Opera Hotel Edition

Changing Passwords in an OPERA System

Version 5.x
April 2014

CONFIDENTIAL AND PROPRIETARY: For use by MICROS Associates, Agents, and Clients Only

Opera Hotel Edition Changing Passwords in Opera

Copyright
2014 MICROS Systems, Inc. All rights reserved. No part of this publication may be reproduced,
photocopied, stored on a retrieval system, or transmitted without the express prior written
consent of the publisher. MICROS Systems, Inc. retains the right to update or change the
contents of this document without prior notice. MICROS Systems, Inc. assumes no responsibility
for the contents of this document.
OPERA is a trademark of MICROS Systems, Inc.
On Oracle and the On Oracle logo are trademarks of Oracle Corporation.
Information in this document is subject to change without notice.
MICROS Systems, Inc. makes no warranty of any kind with regard to this material, including but
not limited to the implied warranties of marketability and fitness for a particular purpose.
MICROS Systems, Inc. shall not be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing, performance, or use of this material.

MICROS Systems, Inc.

Fidelio Technologies Inc.
2640 Golden Gate Parkway, Suite 211
Naples, FL 34105
Voice: (239) 643-7999 / Fax: (239) 643-7911

Author:
Contributors:

MICROS SYSTEMS, INC.

PAGE 2
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Table of Contents
INTRODUCTION.............................................................................................4
OPERATING SYSTEM ACCOUNTS....................................................................5
ORACLE USER ACCOUNTS ..............................................................................7
ORACLE OPERA ACCOUNTS ............................................................................9
CHANGING AN ORACLE USER PASSWORD ...................................................10
CHANGING PASSWORD USING OAPPCFGED ................................................12
OPERA CLUSTER SOLUTION.........................................................................16
OEDS ...........................................................................................................17
OXI..............................................................................................................18
OPERA USER ACCOUNTS ..............................................................................19
CHANGING SYS PASSWORD WITH DATAGUARD ..........................................20

MICROS SYSTEMS, INC.

PAGE 3
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Introduction

Purpose
This document describes what types of password protected user accounts are used in an OPERA system.
The implications of making changes to the passwords, and the procedures for changing selected passwords.

Intended Audience
This document is intended for all staff of Micros-Fidelio, its partners, customers and contractors which deal
with system security. This document should not be released for general usage.

MICROS SYSTEMS, INC.

PAGE 4
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Operating System Accounts

Generally, all operating system accounts can have their passwords changed without direct implications to
OPERA. The exception to this is an Opera service account, often named OperaService or OracleService which
might be present in older systems.

Domain Accounts
Domain\administrator: The password of this account is generally not known to Micros-Fidelio staff. It
may be changed by the customer at will. It may be used in the backup system and the customer should
take that into consideration before making the change.

Domain\operasupport: This account may go under a different name. It is the account which is known
to Micros Fidelios OPERA support team to allow them to log on to the servers. It is normally a simple
domain user with local administrator privileges on the OPERA servers. If this password is changed, the
customer must put in place a process whereby the property has access to the password at all
times should the need for support arise. MICROS Fidelios OPERA support team they may not be able to
offer support at the time of the call without being given the password to this or a similar account.
Domain\operaservice: This account may go under a different name. It is the account which runs
OPERA services on some older systems. Normally, it is a simple domain user with local administrator
privileges on the OPERA servers. If this password is to be changed, MICROS Fidelios OPERA support team
must be informed beforehand in order for advice to be given. The OPERA services will need to be
reconfigured to use the new password.

Domain\BackupUser: This account may go under a different name. It is the account which is set up to
run the backup services on the backup server and will also often be used for inter-server communication by
the backup processes. It is often a domain administrator and will always be a domain backup operator.
It may be changed but the backup configuration and services may require updating with the new password.
Other domain accounts: It is unlikely that changing the password of other domain accounts will have any
effect on the OPERA system, but each installation could have unique circumstances that should be reviewed
when formulating plans and procedures for regular password changes.

Local Accounts
Local \administrator: This account was created when the operating system was installed.
Other local accounts: It is unlikely that changing the password of other local accounts will have any effect
on the OPERA system, but each installation could have unique circumstances that should be reviewed when
formulating plans and procedures for regular password changes.

Accounts on Clustered Servers

Customers with OPERA V2 or OPERA V3 clustered servers are strongly advised not to amend the OPERA
cluster user password. This is a task which should be undertaken by OPERA Technical Services.
Customers with OPERA V4 or OPERA V5 clustered servers are reminded that any changes to local passwords
must be the same on both servers.

Changing Operating System Account Passwords

MICROS SYSTEMS, INC.

PAGE 5
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Domain Accounts: On the domain controller use the User Maintenance Tool to change the password. In
programs which use the password, such as Backup Exec, amend the configuration with the new password.
Local Accounts: Use the Local Users section of the Computer Management Tool to amend the password. In
programs which use the password, such as Backup Exec, amend the configuration with the new password.

MICROS SYSTEMS, INC.

PAGE 6
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Oracle User Accounts

Oracle System Accounts

SYS: The password can be changed, but for RAC environments, it will have to be done on each node so that
the ORAPWD file will get changed on each node.. The SYS password may be used as part of the backup
configuration and any changes will have to be reflected there. Any changes must include a comprehensive
field plan so that all properties have a system in place to access and know the password at all times in case
it is needed for MICROS to provide support.
SYSTEM: The password can be changed. The SYSTEM password may be used as part of the backup
configuration and any changes will have to be reflected there. Any changes must include a comprehensive
field plan so that all properties have a system in place to access and know the password at all times in case
it is needed for MICROS to provide support.
OLAPSYS: The password can be changed. Any changes must include a comprehensive field plan so that all
properties have a system in place to access and know the password at all times in case it is needed for
MICROS to provide support.
OUTLN: The password can be changed. Any changes must include a comprehensive field plan so that all
properties have a system in place to access and know the password at all times in case it is needed for
MICROS to provide support.

Oracle Locked Accounts

ANONYMOUS, DBSNMP, DIP, EXFSYS, MDSYS, ORDPLUGINS, ORDSYS, SI_INFORMTN_SCHEMA, TSMSYS,
WMSYS, XDB: These Oracle internal user accounts are locked and the passwords should not need to be
changed. If they are to be changed, Micros Fidelio Professional Services support must be consulted prior to
the change. The customer must ensure that a record of the changes can be made accessible to Micros
Fidelio OPERA support on demand.
Refer to Oracle Metalink Note: 160861.1 : Oracle Created Database Users: Password, Usage and Files
References
Running the commands below while logged into SQLPlus as the SYS user will show current Oracle user
account information.

set pages 999

set lines 120
select username, account_status, lock_date, expiry_date from dba_users order
by 1;

MICROS SYSTEMS, INC.

PAGE 7
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

If the account status is OPEN, then it is Open for logins.

If the account status is LOCKED or EXPIRED & LOCKED, then the account is not accessible for login.
The EXPIRY_DATE column will show the expiration date of an account, if empty, the account will not expire.
To unlock an account, do the following as SYS in SQLPlus (Example below would be to unlock the OPERA
user account):

alter user <username> account unlock;

Replace <username> with the name of the account you would like to unlock. For example, to lock the
OPERA account:

alter user OPERA account unlock;

To lock an account, do the following (Example below would be to lock the OXI user account):

alter user <username> account lock;

Replace <username> with the name of the account you would like to lock. For example, to lock the OXI
account:

alter user OXI account lock;

NOTE: An account can become locked if there have been multiple attempts to log into that account with an
incorrect password.

MICROS SYSTEMS, INC.

PAGE 8
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Oracle OPERA Accounts

OPERA: The OPERA password can be changed. Following the change the Application Server configuration
will need to be updated; the Property Interface (IFC7 and IFC8) configuration will need to be updated;
Other external system configurations (OEDS, iDeas, etc) will have to be updated;
The OXI, OXIHUB, OPERA_PMS, BI, and VISION synonyms will have to be refreshed.
Changing the OPERA password is a serious change to the OPERA system and must include a comprehensive
field plan so that all properties have a system in place to access and know the password at all times in case
it is needed for MICROS to provide support.

OXI: The OXI password can be changed. Following the change the Application Server configuration will
need to be updated;
The OXI and OPERA synonyms will have to be refreshed.
Changing the OXI password is a serious change to the OPERA system and must include a comprehensive
field plan so that all properties have a system in place to access and know the password at all times in case
it is needed for MICROS to provide support.

OXIHUB: The OXIHUB password can be changed. Following the change the Application Server
configuration will need to be updated;
The OXIHUB and OPERA synonyms will have to be refreshed.
The OXIHUB Monitor configuration will have to be updated.
Changing the OXIHUB password is a serious change to the OPERA system and must include a
comprehensive field plan so that all properties have a system in place to access and know the password at
all times in case it is needed for MICROS to provide support.

TRAIN/TRAINING/OPERA_TRAIN: The passwords for any training or testing schemas can be

changed. Following the change the Application Server configuration will need to be updated;
If there are OXI, OXIHUB, BI, or VISION schemas associated with these schemas, then the synonyms will
have to be refreshed. Normally there are no ancillary schemas associated with training related schemas, but
there may be with environments that exist for testing purposes.

MICROS SYSTEMS, INC.

PAGE 9
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Changing an Oracle User Password

This work should only be undertaken by a person with skills in Oracle Database Administration.
Use SQLPlus, or a similar tool, to access the database as SYSDBA. Enter the following command to change a
users password:

alter user <username> identified by <newpassword>;

Replace <username> with the username you would like to change and <newpassword> with the users
new password. For example, to change the password for the SYS user to thenewpassword:

All changes to Oracle OPERA Account passwords must be documented and supplied to MICROS OPERA
Support or other MICROS staff when support is required.
NOTE: We discourage the use of the special characters #, @ and $ from being used in Oracle passwords.
For the SYS user only: After changing the password, go to the ORACLE_HOME\database directory and
confirm that the Oracle password file date/time was changed as well.
For RAC installations, the ALTER USER command will need to be run on each node when changing the SYS
user password. Also confirm on each node, that the password file was changed.

MICROS SYSTEMS, INC.

PAGE 10
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

After changing the password always make certain that connections can be made using SQLNet.

If the password being changed belongs to an OPERA Oracle user, such as OPERA, OXI, OXIHUB, etc, then
the OPERA Application Configuration Editor (OAppCfgED) will need to be used to change the password on
EACH app server and the services restarted. This is done after the password is changed in SQLPlus.

MICROS SYSTEMS, INC.

PAGE 11
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Changing password Using OAppCfgED

After an Opera Oracle user password has been changed via SQLPlus, the configuration on each application
server needs to be changed to reflect the new password and the services restarted.
To do this:
1.

Launch the OAppCfgEd.exe from the \micros\opera\tools directory on the application server.

2.

Prior to the first screen a confirmation pop-up box will appear asking whether you want to open the
OAppCfgEd in read-only mode or write mode. If you open the OAppCfgEd in read-only mode then
you can neither add nor modify the configuration entries.

Select No when asked to confirm whether you want to open the application in Read-only mode.

MICROS SYSTEMS, INC.

PAGE 12
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

3.

In the tab labeled Connections, select the schema which had the password changed via SQLPlus
and then click Edit .

4.

In the box labeled Password, type in the new password and then click Update Config .

MICROS SYSTEMS, INC.

PAGE 13
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

5.

To verify the configuration is correct, click Check Connect. To confirm a connection to the
database is available when you the word Connected. will appear at the bottom of the output
window.

6.

If you need to update the password for additional schemas, click Back, and then follow the above
steps for each schema you would like to update.

7.

After you have updated the password for all required schemas, click Restart Services .

MICROS SYSTEMS, INC.

PAGE 14
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

8.

After services have restarted, exit OAppCfgEd by clicking Close .

MICROS SYSTEMS, INC.

PAGE 15
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Opera Cluster Solution

In an Opera Cluster Solution configuration, the Opera Cluster Control Utility recreates the password file each
time when a database failover happens.
When the SYS password is the default password, the user will not be prompted in order to initiate the fail
over. The new password file will be created using the default password.
When the default SYS password has been changed by following the instructions earlier in this document, the
user will be prompted for the new password.

When the correct password is provided, the database failover will occur and a new password file will be
created on the receiving node using the password provided.

MICROS SYSTEMS, INC.

PAGE 16
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

OEDS
After an Opera Oracle user password has been changed via SQLPlus that is used by OEDS, the OEDS
configuration on each OEDS server needs to be changed to reflect the new password.
Go into the OEDS Configuration Editor.
Change the password and then click the Not Connected button.

After a few seconds, the button should show Connected.

Now keep clicking Next until exiting out of the OEDS Configuration Editor.

MICROS SYSTEMS, INC.

PAGE 17
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

OXI

For OXI

1.
2.
3.
4.

Copy OXI_PROCESSOR_SHELL.EXE from Micros\Opera\Tools\OXI\INTERFACE folder on

production application server to local machine, this is important to get the latest processor wizard.
Execute it on the local machine, navigate through the wizard pages, all options except the
connection can be left as they are to retain current settings.
Once the wizard is completed successfully, registry would reflect the new value.
Make sure that the restarted services are able to connect by reviewing the corresponding log files.
For OXIHUB

1.
2.
3.
4.

Copy setup.exe from Micros\Opera\Tools\OXI_HUB\INTERFACE folder on production

application server to local machine, this is important to get the latest processor wizard.
Execute it on the local machine, navigate through the wizard pages, all options except the
connection can be left as they are to retain current settings.
Once the wizard is completed successfully, values in registry would reflect the new value.
Make sure that the restarted services are able to connect by reviewing the corresponding log files.

MICROS SYSTEMS, INC.

PAGE 18
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Opera User Accounts

SUPERVISORY User Accounts

The password of the SUPERVISOR user may be changed, but must include a comprehensive field plan so
that all properties have a system in place to access and know the password at all times in case it is needed
for MICROS to provide support.
In multi-property sites where there may be more than one SUPERVISOR user, the same applies to all
SUPERVISOR users.

Special Function User Account

For some installations, special function user accounts have been created to work with OEDS applications or
with third party applications. The passwords may be changed but must also be changed in the configuration
of the corresponding application. When passwords of any type are changed, the customer must set up and
maintain a comprehensive field plan so that all properties have a system in place to access and know the
password at all times in case it is needed for MICROS or 3rd party software vendors to provide support.

Ordinary User Accounts

The maintenance of ordinary user accounts is a normal maintenance function of the site. Passwords may be
changed if and when desired. Ordinary Users can change their own password.

Changing an OPERA User Password

One OPERA user may change the password for another user as long as the user that will implement the
change has been granted the Add, Modify or Delete User Groups permission.

Support
Customers are strongly advised to consult with Micros Fidelio OPERA Account Management
before planning any password changes.
MICROS Fidelio OPERA Support does not perform password changes; therefore clients must put in place a
comprehensive field plan so that all properties have access to passwords at all times in case they are
needed for MICROS support.
Failure to do this may result in MICROS Fidelio OPERA support not being able to provide support.

MICROS SYSTEMS, INC.

PAGE 19
CONFIDENTIAL AND PROPRIETARY

APRIL 2014

Opera Hotel Edition Changing Passwords in Opera

Changing SYS password with Dataguard

The following details how the SYS password should be changed in a Dataguard environment.
Immediately below is from Oracle Document 806703.1
Its advisable to follow the steps below when you are planning to change the SYS password in PRIMARY
Step 1: Defer the remote archival destination (log_archive_dest_state_n) parameter in primary. In case of
RAC defer LOG_ARCHIVE_DEST_STATE_n in all nodes.
Alter system set LOG_ARCHIVE_DEST_STATE_n=defer;
Step 2: change the password in primary
Alter user sys identified by <password>;
Step 3: Copy or Recreate the password file in standby. In case of RAC, shutdown all instance of standby
before recreating the password file.
Copy D:\oracle\1020\database\orapwSID to \\nameofstandbyserver\D$\oracle\1020\database\orapwSID
Or
orapwd file=orapwSID password=oracle entries=5 FORCE=Y
Step 4: Enable the remote archival destination (log_archive_dest_state_n) parameter in primary
Alter system set LOG_ARCHIVE_DEST_STATE_n=enable;
If the password is already changed, and/or you are getting ORA-16191 during log shipping then follow
the below action.
Action: Copy the password file from PRIMARY to STANDBY (OR) recreate the password file in standby with
the same password using the ORAPWD command.

Note: Below should only be done if unable to copy over current Primary orapwSID file to the Standby
database server(s).
Below is a syntax example, replace SID with the actual SID of the instance. This is to be done from the
command line with the DATABASE home set:
orapwd file=orapwSID password=oracle entries=5 FORCE=Y

The Oracle password file is found in D:\Oracle\1020\Database and is typically PWDOpera.ora.

The ENTRIES parameter is the number of concurrent SYSDBA users that can connect to the DB. You can
eliminate this entry and accept the default value.
The FORCE parameter is used to overwrite the previous file.
The New Password MUST be the same as the new SYS password on the primary server.

After the password has been modified on the standby server(s), ensure that archive logs are being applied
and no errors seen in the alert log.
select sequence#,applied from v$archived_log order by sequence#;

MICROS SYSTEMS, INC.

PAGE 20
CONFIDENTIAL AND PROPRIETARY

APRIL 2014