No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

BMU admin password reset EC3.0

Publication Date:  2017-09-12 Views:  65 Downloads:  0
Issue Description

Customer does not remember Admin password for BMU web portal

Alarm Information

N/A

Handling Process

1.Get the information of database

Note: if you know
database IP/Port/user/password already, this step can be skip .

Login the path:

$/eSpace_UC/eSpace_UC_Server/Server/BMU/webapps2/ROOT/WEB-INF/classes

Open the configuration file jdbc.properties in this path.




You can find the information in the picture as the example
Database IP 10.184.50.169

Database listening Port1521
Database servicesUCC

Database userBMU_30

2. connect the database and execute the SQL command

Step1:connect oracle database.

a)    Use the PLSQL  Developer login oracle database


Enter the username/password/ip:port/services login.

b)      Login SQL PLUS

Execute the command:

1.su – oracle

2. sqlplus  usernamer/password@services(replace with the actual value as you found in step1)

Step2: execute the SQL command:

update t_bme_operator set password='[103, 20, 12, -55, -71, 74, -8, -44, 119, -46, 11, -61, 3, 95, 17, 61, -106, 45, 83, 70]',column_5='[42, 65, 63, 58, -16, -56, 68, -64]' where name='admin';

commit;

*****IMPORTANT *** For Oracle the semicolon is very important to indicate the end of a command ";"

Step3 : restart the BMU,

Switch the 2 nodes-cluster and switch back, services will be restart.

Check the status : hastatus –sum,  you will find the information as
below:


Switch the cluster hagrp -switch empcluster_group -to ecc-emp2

·        
eupp_empclusterresource group name, replace by actual

·        
ecc-emp2standby server name, replace by actual


Step4:

The password will
be:  1qaz@WSX



Root Cause

Customer forgot /lose password

Solution

reset Admin password with previous procedure

Suggestions

All changes in production environment should be done by customer, perform a database backup and under non business hours with a maintenance window. If customer is not able to perform those operations local office may need to deliver a MOP

END