In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)05/31 Report--
This article mainly introduces "how to migrate Oracle database from Linux x86 stand-alone to Solaries". In daily operation, I believe many people have doubts about how Oracle database migrates from Linux x86 stand-alone to Solaries. Xiaobian consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts about "how Oracle databases migrate from Linux x86 stand-alone to Solaries". Next, please follow the editor to study!
Take a look at the directory structure first
1. Select test environment
two。 Modify the scan ip of a rac cluster
3. Select one of the nodes to create a new directory
4. Create a new tablespace in ASM
5. Upload logical backup files for production database
6. Production data restore
7. Modify database user password
8. Modify configuration information in the database
9. Modify the database password and never expire
10. Modify database password error do not lock user
11. Collect statistics manually
twelve。 Modify the database connection in the application to Service connection
13. Start the application and verify the deal in turn
1. Select test environment
(note: a ready-made test environment is selected here for verification to reduce the time spent on test environment preparation. )
(1) Select a set of test environment, database IP is 100.100.100.103, application server IP is 100.100.100.194
(2) Log in to the application server and the database server, close the application and database, and shut down the database server 100.100.100.103.
(3) execute the command ping 100.100.100.103 to ensure that the database server is shut down.
two。 Modify the scan ip of a rac cluster
(note: here you choose to directly modify the scan ip of the RAC cluster to 100.100.100.103 to ensure that the thread pool in the application can be connected after startup. )
Refer to the article for the procedure:
Http://blog.itpub.net/31394774/viewspace-2217511/
3. Select one of the nodes to create a new directory
Note: considering the small amount of production data of the system at present, it is convenient and quick to use data pump expdp to back up.
Create a new directory on the cwgsdb1 server
Oracle@cwgsdb1:~$ mkdir-p / u01 Production on Tue Oct Production on Tue Oct oracle@cwgsdb1:~$ mkdir-p / u01 Production on Tue Oct Production on Tue Oct 23 22:08:42 oracle (c) 1982, 2013, Oracle. All rights reserved.Connected to:Oracle Database 11g Enterprise Edition Release 11.2.0.4.0-64bit ProductionWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,Data Mining and Real Application Testing optionsSQL > create or replace directory dpdata1 as'/ u01 * Create a new tablespace in ASM
(note: only part of the tablespace is enumerated here, and the tablespace is established in the ASM file system)
Create tablespace cams_core_idx datafile'+ DATADG/CAMS/DATAFILE/CAMS_CORE_IDX_001.dbf' size 100m AUTOEXTEND ON next 200m maxsize unlimited;create tablespace cams_core_tab datafile'+ DATADG/CAMS/DATAFILE/CAMS_CORE_TAB_001.dbf' size 100m AUTOEXTEND ON next 200m maxsize unlimited;create tablespace cams_core_lob datafile'+ DATADG/CAMS/DATAFILE/CAMS_CORE_LOB_001.dbf' size 100m AUTOEXTEND ON next 200m maxsize unlimited;5. Upload logical backup files for production database
Oracle@cwgsdb1:~$ cd / u01 Oct Oct camsData20181017.dmp-rw-r--r-- camsData20181017.dmp-rw-r--r-- 1 oracle oinstall 335274 Oct 23 22:54 camsData20181017.log6. Production data restore
Oracle@cwgsdb1:/u01/app/oracle/dump$ impdp\'/ as sysdba\ 'DIRECTORY=dpdata1 DUMPFILE=camsData20181017.dmp SCHEMAS=xxx,yyy logfile=impdp_camsData20181017.log7. Modify database user password
(note: the password of the test environment is inconsistent with that of the production environment, and the user password of the production environment needs to be modified)
Alter user XXXX dientified by 123456. Modify configuration information in the database
(1) modify the configuration information with user / password in the database
(2) modify the configuration information with IP address in the database
(3) modify the configuration information with path in the database (note: if the storage path in the production environment is inconsistent with the test)
9. Modify the database password and never expire
(note: if there is a DBA to change the password on a regular basis, do not perform this step)
SQL > set linesize 200 leading SQL > col limit for a30 leading SQL > select * from dba_profiles where profile='DEFAULT' and RESOURCE_NAME like 'PASSWORD_%' PROFILE RESOURCE_NAME RESOURCE LIMIT -DEFAULT PASSWORD_LIFE_TIME PASSWORD 180DEFAULT PASSWORD_REUSE_TIME PASSWORD UNLIMITEDDEFAULT PASSWORD_REUSE_MAX PASSWORD UNLIMITEDDEFAULT PASSWORD_VERIFY_FUNCTION PASSWORD NULLDEFAULT PASSWORD_LOCK _ TIME PASSWORD 1DEFAULT PASSWORD_GRACE_TIME PASSWORD 76 rows selected.
Now explain the values of the parameters in detail:
The life cycle of the PASSWORD_LIFE_TIME password (in days). After this period, the password may expire automatically. Whether it expires depends on whether PASSWORD_GRACE_TIME is set.
PASSWORD_REUSE_TIME limits the number of days in which passwords cannot be reused. The default value is UNLIMITED.
The PASSWORD_REUSE_MAX feature is specific to PASSWORD_REUSE_TIME, indicating that in order to reuse the current password within the time specified by the parameter PASSWORD_REUSE_TIME, at least the number of times the password needs to be changed (of course, the modified password must be different from the current password, because, after all, there are restrictions on the PASSWORD_REUSE_TIME feature)
PASSWORD_VERIFY_FUNCTION can set the password complexity of oracle users, such as password length > = 10, which must contain letters / numbers, etc.
PASSWORD_LOCK_TIME is followed by the FAILED_LOGIN_ATTEMPTS parameter, the time when the password is automatically locked. After this time, the system automatically unlocks the account the next time you log in.
PASSWORD_GRACE_TIME follows the PASSWORD_LIFE_TIME feature, and if the expiration of the PASSWORD_LIFE_TIME has expired, the PASSWORD_GRACE_TIME is a grace (grace or extension) of the password life cycle, indicating the number of days after the password expires. During this time, if we log in to the system, there will be a prompt that the system will expire within a few days.
SQL > ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;Profile altered.SQL > select * from dba_profiles where profile='DEFAULT' and RESOURCE_NAME like 'PASSWORD_%' PROFILE RESOURCE_NAME RESOURCE LIMIT -DEFAULT PASSWORD_LIFE_TIME PASSWORD UNLIMITEDDEFAULT PASSWORD_REUSE_TIME PASSWORD UNLIMITEDDEFAULT PASSWORD_REUSE_MAX PASSWORD UNLIMITEDDEFAULT PASSWORD_VERIFY_FUNCTION PASSWORD NULLDEFAULT PASSWORD_LOCK _ TIME PASSWORD 1DEFAULT PASSWORD_GRACE_TIME PASSWORD 76 rows selected.10. Modify database password error do not lock user
(note: in order to prevent users from mismatching passwords or malicious attacks lead to password locking, resulting in production failure)
SQL > select * from dba_profiles where profile='DEFAULT' and RESOURCE_NAME like 'FAILED%' PROFILE RESOURCE_NAME RESOURCE LIMIT-- DEFAULT FAILED_LOGIN_ATTEMPTS PASSWORD 10
The number of attempts to log in if FAILED_LOGIN_ATTEMPTS does not know the password. After reaching this number, the account is automatically locked.
SQL > ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;Profile altered.SQL > select * from dba_profiles where profile='DEFAULT' and RESOURCE_NAME like 'FAILED%' PROFILE RESOURCE_NAME RESOURCE LIMIT-- DEFAULT FAILED_LOGIN_ATTEMPTS PASSWORD UNLIMITED11. Collect statistics manually
Exec dbms_stats.gather_schema_stats ('XXXX'); 12. Modify the database connection in the application to Service connection
(note: the previous database is a single instance, and some of the database connection configuration information is SID connection, which needs to be changed to Service connection and RAC cluster connection through scan ip)
DataSource.url=jdbc:oracle:thin:@100.100.100.103:1521:cams
Modify to
DataSource.url=jdbc:oracle:thin:@100.100.100.103:1521/cams13. Start the application and verify the deal in turn
Start the application sequentially, test multiple groups of transactions across subsystems, and then view the message and success status of the transaction on the data bus monitoring platform.
At this point, the study on "how to migrate Oracle database from Linux x86 stand-alone to Solaries" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.