Starting Shared Server before using SQL *Plus

$ORACLE_HOME/bin/oracle -shared_servers

$ sqlplus /nolog
SQL> SET SERVERNAME=localhost/ORCL;
SQL> CONNECT scott@localhost/ORCL SHARED_SERVERS;
Enter password: tiger

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0 - 64bit Production

SQL>

Creation of Internal Password in Oracle 13c

Historial Noted regarding Server Manager prior to Oracle 9i

1. Know the executable name: You should now know the name for your Server Manager executable, so let us start it. If you are not running Oracle software, just make sure you know the executable name for the version that you will eventually be running. If you are running Oracle, go ahead and issue the command. If you are on Windows, you will need to open a command prompt window first. The following example was done under NT using Oracle release 8.0.4: The following commands have been deprecated since Oracle Server Manager has been retired since Oracle 9i.
   Note: The following information is for only for historical reference.

   C:\ORANT\BIN>svrmgr30
   Oracle Server Manager Release 3.0.4.0.0 - Production
   (c) Copyright 1998, Oracle Corporation.
   All Rights Reserved.
   Oracle8 Release 8.0.4.0.0 - Production
   PL/SQL Release 8.0.4.0.0 - Production
   SVRMGR>
   

2. Connecting to a Database using Server Manager: After you start Server Manager, the next step is to connect to a database. You can do this by using the CONNECT command. The following example shows one way to connect to your default database. The internal keyword tells Server Manager that you want to connect as an administrative user.
3. Connecting as Administrative User: There are two basic ways to connect to an Oracle database:
   • as an administrative user and
   • as a normal user.
4. Connect as DBA or User: For 90% of the tasks that you do, you will find that you can connect either way and it will not matter. Any priviledged user can connect normally to the database and still be able to
   • run queries,
   • create and alter schema objects.
   
   However, to start up or shut down a database, recover a database, or create a new database, you must be connected as an administrator.
   The keyword internal represents one way to tell Server Manager that you want to connect as an administrator. Two other keywords may also be used. These are
   • SYSDBA and
   • SYSOPER.
   In order to use SYSDBA and SYSOPER, you must configure a database password file. We will do that in, Managing Users and Connectivity, the next course in this series.
5. Password Creation: Depending on choices that you made when you installed Oracle, you might be prompted for a password. This is a special password known as the internal password. The default for that password is “oracle,” but if you chose a different internal password when you installed Oracle, use that. If someone else created this database, and you do not know the internal password, then you should ask the person who created the database to help you connect to it. Go ahead and try connecting to your default database. There exists a GUI version of Server Manager, but we will not address the GUI version in this course.
6. Legacy GUI Version of Oracle Server Manager: For UNIX users, Oracle supplies a GUI version of Server Manager. The command to start it is: svrmgrm. The “m” at the end of the command stands for “Motif”. Motif is an X-Windows-based windowing manager that you need in order to use the GUI version. To start the GUI version of Server Manager from an X-windows client, you first open a Telnet session, then issue the svrmgrm command. Enterprise Manager is Oracle's flagship database administration tool, and it's GUI-based. If you want to learn a GUI administration tool, you are much better off focusing your efforts on learning Enterprise Manager.
7. GUI Tool to manage Oracle Databases: In 1996, Oracle made a first attempt at releasing a GUI tool to manage its databases. This was Oracle Server Manager, which featured a 1) command line and 2) GUI interface. In the past, most DBAs resorted to using only the command line interface of Server Manager, called Server Manager/Line Mode. This was because at that time it was easier to get things done using the command line interface. In addition, the first few releases of the GUI interface had limited administrative capabilities. Oracle then released a new version, Oracle Enterprise Manager. OEM 9.2 was released in 2002, which was when larger numbers of DBAs first started using Enterprise Manager. The console product was Java-based and had to be installed as a separate product on each workstation accessing the central repository of Enterprise Manager. This OEM 9.2 was a stand-alone console mode without a repository and a mode that connected to a central repository. Many DBAs used the stand-alone mode without the repository. As a result, there was no central repository of database information in many sites even though OEM 9.2 was being used.
8. In 2004, Oracle rewrote the product with a new architecture based on its application server technology Oracle 9i. The console was now browser-based and could be accessed from any workstation on the corporate network without the need to install software on any workstation. The only installation required was the 1) repository and 2) server agents. The stand-alone mode was no longer possible, thus forcing the use of a centralized repository. The Enterprise Manager product that allowed management of multiple databases and servers was named Grid Control, after use of the 'g' letter in the Oracle 10g database. The emphasis it laid on the Grid in the year 2006 was for the future of computing. DBAs can understand how Grid Control can assist in the daily database administration activities. In addition, the DBA can make the automation of jobs without scripts, removing much of the dependence on UNIX shell scripts and cron jobs.

SQL> connect internal

Grid Control