The growth of Blue-Chase DBA (5): No talking about business, annoying application system

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

An individual's growth record on Oracle's path, with blue self-metaphor, to share growing emotions, horizons and technological changes and growth. Sensitive information is replaced in English, and will not disclose any corporate secrets, purely for technology sharing.

Creation is inspired by self-reflection and record. If you can have a little help or sympathy for the beginning of the library friends, gratified unceasingly.

Welcome to make bricks, such as the technical details of the error, please leave a message or e-mail ([email protected]) indicated, greatly appreciated.

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

If you want to jump high, you need to learn to squat down first.

--Dark blue

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

This is a personal record of the growth of the notes, since the step into the blue Sea of Oracle, inevitably all the way to the rush and constant test. By this story and friends to share the blue growth process.

I do not know when the blue has a kind of said not out of the obsession, obsessed with its breadth, obsessed with its depth, obsessed with the near and far away.

And don't know from when, looking at Oracle Red dazzling, illuminating a light, the unknown and confused at their feet began to show a little bit of life's enrichment and youth feedback.

Step forward on the path to the DBA's dream.

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

2014 Beijing

Two days of running to run, the problem shifted to the research and development, have to spit groove, link, the system still needs to continue to build and improve, business layer, site layer, the implementation layer of different treatment situation, with the emergence of different field problems. The appearance of this problem seems very simple, but let the implementation of staff costs a half-day time, the pain is painful to let people physically and mentally exhausted. Around for a long time, is not some listening dizzy, next, I come to recall this and the business layer has a close relationship with the implementation of deployment.

Scenario: In order to complete the deployment of the migration project, the original application system, the database to migrate to the new server, the deployment of the client, the environment is a 64-bit Win7 system (explained that the production Environment application server, database server is separate, and this deployment as a scientific research project, the contents of which is inconvenient to elaborate, Understand this on a server on the line). A application of Java development, B/s architecture. b, C and other application clients are B/s architecture, but based on 32-bit system development. It is this simple technical detail that starts to trigger a continuous business problem.

After the main system a application redeployment is complete, seemingly everything is normal, in the background a bit of trouble, changed the password, and finally use the Super Administrator user login. However, when the task is completed, the problem appeared in front of the technical staff, a maintenance page can not be accessed normally, the issue of permissions. Continuous Click Testing, the business layer of new problems, a processing program is not available. Surprisingly, there was no objection to this deployment. Where did the problem arise? Follow the prompts to step through the wrong line. Due to the lack of a comprehensive deployment manual at hand, it is suggested that the problem is: one JDK is causing the inability to process. Search, download, install, continue troubleshooting, and discover that some features are missing. At this time contact research and development, business script mail came, for operation and maintenance work, some sweat, run scripts, problem solving. At this time a blank face to understand the business process and technology implementation of the relationship between the end there is no clear demarcation line. It can be imagined that if in the face of this problem, through the technical aspects of the wrong, it is a bit of a fantasy, I am afraid, in addition to the development of a completely new out there will not be any correct solution, because this is the business needs. That's the problem with the business layer, it's that simple. The development has the business script, runs, realizes is to have some function table to create under, the Function item association, the permission assigns under, and so on and so on, the problem solves. It is simple to say that the angle of thinking is the key, coordination, feedback sometimes more than the technology itself.

This is only a application system leak problem, not to mention the annoying B, C, D application System, this time can be said to be annoying unceasingly. There is a problem with the client's program, access. Once again, the developers, continue to contact. The next step is to anticipate the effect. Good, re-mail, replace files, reset. Are we done? This time, the business layer does not know how, the program seems to be wrong. This is a serious problem, because in this series of business systems, there is a key "backbone" system (technical details are not disclosed), can be understood as an upload to release the management platform, based on the main business system, maintain the consistency of all the system information (there is no feeling a bit like the undo segment in Oracle, Maintain a consistent reading. Haha, here is purely for the play talk). Because this application deployment is not working properly, this series of migrations appears to be complete, but it is back to the starting point. This time, contact development again. The personnel in the field collapsed, and the researchers collapsed. A couple of emails. The configuration has no effect, can not continue to go on. Copy all the Tomcat logs away, this time the need for research and development personnel to visit the scene (here, people can not help but recall, once also because of the company's business problems, project leader, implementation personnel, maintenance personnel, developers, party leaders, party a crowd of engineers gathered to the scene of the spectacular scene, Haha, again play talk ~ ~ ）。 Of course, the situation is still manageable. There is still one day to adjust for the last business deployment. According to common sense experience, this client problem, after the development of the scene, according to the actual environment, adjust the corresponding package, configuration files, the problem will be resolved. Around for a while, just hold the paragraph here.

In retrospect, many of this problem is not technically. Think about technology-related aspects, such as the need to configure TNS, monitoring, middleware deployment, tuning, data migration, and so on, is not the cause of this problem. The problem leaks in the business application, the field system environment change, the different business document adjusts, the update.

This is referred to as the "Business Requirements", Oracle technology also needs to land, sometimes the problem-solving ideas may be higher than the technology, technology exploration needs business support.

*************************************** not to be continued ***************************************

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

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

The growth of Blue-Chase DBA (5): No talking about business, annoying application system