Blue growth notes-Chase DBA (3): antique operations, data import and export problems, dba Import and Export

Blue growth notes-Chase DBA (3): antique operations, data import and export problems, dba Import and Export
Blue growth note-chasing DBA (3): importing and exporting data on antiques becomes a problem

************************************ Statement ***************************************

Personal Growth records on the oracle Road, expressed in blue, share the growing emotions, vision and technological changes and growth. Sensitive information is replaced by English and will not disclose any confidential information of the company. It is only used for technology sharing.

The creative inspiration comes from self-reflection and recording. I'm glad to have some help or resonance with the database friends who just started out.

Please leave a message or email (hyldba@163.com) indicating that the technical details are incorrect. Thank you very much.

**************************************** **************************************** ***

The meaning of life is not what you have, but what you choose to pursue,

With the pursuit of goals, life will become meaningful.

-- Deep Blue

************************************* Preface ***************************************

This is an accumulation of personal records. As we enter the blue ocean of oracle, we can't go all the way and continue to test. Share the growth history of blue with database friends.

I don't know when I began to become obsessed with blue. I was obsessed with its wide range, its depth, and its close proximity.

But it cannot be clear from when, watching the oracle red dazzling, illuminating a light in front of the eyes, unknown and confused under their own feet began to reveal some of the enrichment of life and the feedback of youth.

Step by step on the path to pursue DBA's dream.

**************************************** **************************************** ***

September August 4, 2014

Contact the customer today and go to data center A. the IDC environment is quite good. Unfortunately, when we see the actual machine, we are a little disappointed. There is no other idea, but we are disappointed with its performance. Five years have passed, but it is not too long. I have learned that a server has been working normally for 20 years. However, the current version can only be said that the IT industry is developing and changing too fast, not enough, but cannot keep up with the pace of the big era. The decline in server performance can be easily explained: in the initial stage of construction, due to the pilot phase, the daily business volume of the system was very small, so there was no problem during a long period of time. With the strong spread of the system after the sub-branch branches in Weihai, the hidden risks still emerge. It is understood that the server has encountered many small problems in the past year, and the most common method for field operators is to restart the server! So I can't think of a place to replace. I use the word "Antique" to express my mood at the moment. Next, let's take a look at these servers:

(MACHINE 1): Database Server

Dell PowerEdge2950/E53201.86GHz 4-Thread/3.99G memory/136G/Windows2003/Oracle10g

(Machine 2): Application Server

Dell PowerEdge2950/E53201.86GHz eight-Thread/7.99G memory/136G/Windows2003

(Host 3): ftp Server

Dell PowerEdge2950/E53201.86GHz 4-Thread/3.99G memory/136G/Windows2003

(MACHINE 4): Storage

Dell MD3000/1 T/RAID1

The ridiculous configuration, compared with the highest-performance server, is used by the Application Server. The database server is the same as the configuration of an ftp server. It seems strange that two 4G memory machines are labeled with a "Cluster" that has not been torn down. This is like a Cluster environment. Confirm that the two machines are not in the cluster environment. I learned from the engineers responsible for routine control and got the answer. This is the removed solution. Someone from a third-party service provider has been there, renewed for RAC, and configured for storage. However, it cannot be removed. Despite the answer, I saw the red alarm lights flashing constantly in front of my eyes, but I was confused about what happened before.

The current plan was tested: the former third-party service personnel may plan to build a RAC cluster with two machines (machine 1 + machine 3) and use a slightly higher performance server as the application server, the storage uses array storage, and is in security consideration. It does raid1. However, due to cluster setup failure, the solution is changed to a single-instance database, and the data files are stored in the storage, while the application server is not changed, in this way, a server is idle, and the final choice is to build an ftp server for file sharing. According to this idea, the current scenario is formed.

Think about it. If it is me: in Windows, the database cluster will not be built, and the server with better performance will be used as the database server (machine 1 ), then, build an application Cluster Environment (machine 1 + machine 3) for the remaining two servers, and use storage to build a RAID 0 1, to improve the performance bottleneck when backing up data. If you want to get back to your business, you have to go to the customer's current needs.

I have understood that the reason for the transformation of the platform is that the system is unstable, and the performance is reflected in the large number of visitors (the performance difference is obvious when the number of visitors reaches 50 ), the application response latency is serious.

After the conference was attended, the discussion meeting officially started. After some discussion, the customer regards stability and security as the most important consideration. We can decide the Transformation Scheme on our own, but we will not consider the operator difficulty for the moment. Here, I can predict what kind of experience the customer has suffered in the month of server downtime. Everything else can be done as long as the server is stable.

We propose two solutions:

Solution 1: the database server platform is transformed from Windows to Linux, and the Application Server retains the Windows platform to reduce the difficulty of using resident operators;

Solution 2: the database server platform and application server platform are changed to the Linux platform to achieve stability. For operational difficulty, guidance documents are provided to specific operators.

In terms of the backup solution, we provide two solutions:

Recommendation 1: Use scheduled tasks to complete automatic local backup;

Suggestion 2: remote backup and disaster tolerance. The last line of defense of the component will be backed up by our Beijing engineers.

After confirmation, solution 2 is adopted for the transformation. The backup policy is combined with two suggestions to implement two lines of defense for data backup and disaster tolerance. Remote customers serve as the last data security defense line. In this regard, we are switching to the data center.

Continuous use of similar viewing commands to predict the increase in data production: About 30 GB per year, the command reference is as follows:"

Selectcount (1) from t where t. ziduan> = to_date ('20140901', 'yyyymmdd') andt. ziduan <= to_date ('20140901', 'yyyymmdd'); "," select sum (bytes)/20140101/1024/1024 from v $ datafile; "," select sum (bytes) /1024/1024/1024 from dba_free_space ;"

When we further decided on the backup scheme, we could not use the red alarm light.

Trying to back up part of the data in a logical way, the storage read/write speed is quite slow, and it is necessary to identify the storage problems. After reading the data increase and the original data volume, we recommend that you discard the storage array and use the local server. Data growth can be maintained for at least two years. Since the machine configuration is relatively low-end, we recommend that you upgrade the hardware system in the future. The customer also adopted the solution. The upgrade solution is under consideration. After receiving the "call", I feel a bit confused. Solution: Database Server (Machine 2), Application Server (machine 1), ftp component, and local backup server (machine 3 ).

Now, the question is: Back up the data files in the storage, because it is hard to work in this suspicious storage. It was also verified that the data was initially dumped directly from the storage. Start exporting at. Go back to and check that the exported data volume is 15 GB. Check that the exported data volume is 80 GB. That means it may take more than 15 hours to export all the data, which is terrible. 80 GB of data is not big. It takes so long to use it, so I want to use other methods. If you want to copy all the data files to the local server at the system level, run a command like "alter database rename file 'z:/one. dbf 'to 'd:/one. dbf'; "is used to redirect data files and export files through logical backup. This is exactly a cold backup, which needs to be completed when the database is shut down.

Copying data files to the server is also a tough process. Perform cold backup from.

I don't know how long it takes to take a screenshot:

In retrospect, it seems that at around, it was finally completed, and it was not expected to be faster, but at least it was much more practical than it was directly guided by storage. Now you can start exporting.

Check the time, start the logical backup, turn off the display, and return to the hotel. Let's finish the export task at night. What we can do now is to have a rest. May we have everything tonight !~ Anhao ~!.

************************************** Unfinished to be continued ***************************************

Welcome to: Deep Blue Blog: http://blog.csdn.net/huangyanlong

**************************************** **************************************** *********

What are the detailed information and images of Prince tennis?

Choose ke.baidu.com/view/6958.htm?go to Baidu Baike .. Very detailed ..