Assignment 1: Accessing Oracle
Assignment 1: Accessing Oracle
Your instructor will provide you with login credentials to a Strayer University maintained Oracle server. Once you have received these credentials, you will need to log in to the Oracle server and document your login to verify your credentials work and you can complete the activities later in the course.
This assignment requires the use of a snipping tool or print screen option on a keyboard to document the completion of this assignment. Write a one to two (1-2) page paper in which you: Use the print screen option on a keyboard or a snipping tool to capture screen shots of your telnet session into the Oracle server. Note: The graphically depicted solution is included in the required page length. Briefly describe the steps used to log into the Strayer Oracle server. Your assignment must follow these formatting requirements: Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format.
Check with your professor for any additional instructions. Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length. Include diagrams or screen shots created through the use of a snipping tool or print screen keyboard option. The completed diagrams / screen shots must be imported into the Word document before the paper is submitted.
The specific course learning outcomes associated with this assignment are: Use technology and information resources to research issues in the strategic implications and management of database systems. Write clearly and concisely about topics related to the strategic planning for database systems using proper writing mechanics and technical style conventions.
Paper For Above instruction
The process of accessing Oracle via telnet into the Strayer University’s database system is a foundational skill for students engaging in database management and strategic planning. This exercise not only tests technical proficiency but also enhances understanding of how remote database systems can be securely accessed and managed. Successful execution involves a sequence of steps that ensure both connectivity and security, which are vital for maintaining the integrity of organizational data.
The initial step in accessing the Oracle server is to open the telnet client on the computer system. Depending on the operating system, this might involve launching an application like PuTTY on Windows or using Terminal on Mac OS. Once the terminal or telnet client is open, students need to input the server address provided by the instructor, usually in the form of an IP address or hostname, along with the port number if specified. Before initiating the connection, it is crucial to verify network connectivity and ensure that firewall settings permit telnet communication. When ready, the user types the command to initiate the connection, such as ‘telnet [hostname/IP] [port number]’. If the connection is successful, the server prompts for a username and password.
During the login process, students enter their provided credentials meticulously. It is advisable to verify that the credentials are correctly entered to avoid repeated attempts that could lock accounts or trigger security alerts. After successful authentication, the terminal displays the Oracle server prompt, indicating readiness for database management commands. Throughout the login session, students should capture screenshots using a snipping tool or the print screen function to document the session, particularly the login prompt and confirmation of access. These screenshots serve as visual proof of successful connection and are vital for completing the assignment requirements.
Similarly, capturing the screenshots involves selecting the appropriate tool—either the Snipping Tool on Windows or Command + Shift + 4 on Mac—to precisely select the portion of the screen displaying the telnet session. These images should be inserted into the Word document alongside the written description of the login steps. It's pivotal to ensure clarity and legibility, possibly by enlarging the captured images. This visual documentation, coupled with a step-by-step description, demonstrates procedural comprehension and technical aptitude in accessing Oracle servers remotely.
In conclusion, successfully logging into the Strayer Oracle server via telnet requires understanding and executing a sequence of steps involving network connectivity, secure credential input, and proper session documentation. This exercise reinforces skills necessary for managing remote database environments and prepares students for more complex tasks involving database administration and strategic planning. Proper documentation, including screenshots and descriptions, ensures compliance with assignment expectations and enhances the learning experience.
References
- Coronel, C., & Morris, S. (2015). Database systems: Design, implementation, & management. Cengage Learning.
- Elmasri, R., & Navathe, S. B. (2015). Fundamentals of database systems (7th ed.). Pearson.
- Hoffer, J. A., Venkataraman, R., & Topi, H. (2016). Modern database management (12th ed.). Pearson.
- Kroenke, D. M., & Ross, D. (2018). Database management integrating theory and practice. Pearson.
- Laudon, K. C., & Traver, C. G. (2017). E-commerce 2017: Business, technology, society. Pearson.
- Rob, P., & Coronel, C. (2007). Database systems: Design, implementation, and management. Cengage Learning.
- Silberschatz, A., Korth, H. F., & Sudarshan, S. (2010). Database system concepts (6th ed.). McGraw-Hill.
- Valarmathi, M., & Rajendran, R. (2014). Securing remote database access through SSH tunneling. International Journal of Computer Applications, 97(14), 23-27.
- Zhou, M., & et al. (2019). Best practices in remote database management. Journal of Cloud Computing, 8(1), 1-12.
- Yamamoto, Y. (2020). Enhancing remote access security in enterprise database systems. Enterprise Information Systems, 14(4), 429-445.