Sunday, December 3, 2023

Welcome to C# Programming Tutorial site

Home of

(1) Presentation slides

(2) Code to practice Click here to Download Codes

Send PayPal $ any amount to drArchibong@live.com to get access to Codes and Presentation

Friday, July 22, 2022

WINSCP Access Denied using username@host

Problem:

Using Winscp with a username@2.3.4.5: password@hostname

failed connection.

Example: Open sftp://username@server1:P@ssw0rd@server2/ -hotkey="ssh-rsa 1024..."

Solution:

1. Launch winscp.exe

2. Enter username, password, host, port 22

3. Connect

4. Go to the Menu Bar

5. Click Session

6. Click Generate session URL/code

7. Copy script to clipboard

8. Paste to your connection string in your script file

9.Try to connect

ORA-0020- Connected to an idle instance

"Connected to an idle instance" usually means that you connected "AS SYSDBA" and the instance you connected to is not started.

However, if your instance is out of processes, then a non-SYSDBA connection will error out with ORA-0020, and a SYSDBA connection will error out with "Connected to idle instance." It's a little misleading, but that's what happens.

Usually, when this happens, I want to get connected to the instance, so that I can try to figure out which user is causing the problem. One way to do that is to use the 'ps' command to identify some of the oldest server processes, and kill the 3-5 oldest processes, and then quickly try connecting to the database. Once you're in, you can look at things like V$SESSION to try and determine which user(s) is (are) consuming so many connections, and then go from there.

Image result for how to start oracle database

To start or shut down Oracle Database:

Go to your Oracle Database server.
Start SQL*Plus at the command prompt: C:\> sqlplus /NOLOG.
Connect to Oracle Database with username SYSDBA: SQL> CONNECT / AS SYSDBA.
To start a database, enter: SQL> STARTUP [PFILE=path\filename] ...
To stop a database, enter: SQL> SHUTDOWN [mode]

Saturday, January 25, 2020

ORA-12560 Error Solved

Auto-start database

1. go to the command prompt. (as administrator)

Check all your instances running

C;> lsnrctl status

2. Set the Oracle system ID (SID) to

C:> set oracle_sid=ORCL.

3. Run the Net Start command (

C:>net start oracleserviceORCL).

This should resolve the ORA-12560 error in this situation

Reference

https://www.tekstream.com/resource-center/ora-12560-tns-protocol-adapter-error/

Tutorial for Starting Oracle Listener

https://apexapps.oracle.com/pls/apex/f?p=44785:24:1463842410715:PRODUCT:::P24_CONTENT_ID,P24_PREV_PAGE,P24_PROD_SECTION_GRP_ID:6284,141,116

Friday, July 17, 2015

ORA-00838: Memory_target too small

ORA-00838: Specified value of MEMORY_TARGET is too

small

Oracle Tips by Burleson

October 16, 2014

Question: After increasing by "processes" parameter (processes 3000), I got the following ORA-00838 error at database startup time. Note that I am on 12c and I have not set my sga_target or pga_aggregate_target parameter. After re-setting processes=1000 the ORA-00838 error disappeared. Why?

ORA-00838: Specified value of MEMORY_TARGET is too small, 
     needs to be at least 3072M

ORA-01078: failure in 
     processing system parameters

How do I correct the ORA-00838 error?

Answer: The oerr utility shows the cause and action for the ORA-02097:

ORA-00838: Specified value of MEMORY_TARGET is too small, needs to be at least string

Cause: The specified value of MEMORY_TARGET was less than the sum of the specified values for SGA_TARGET and PGA_AGGREGATE_TARGET.

Action: Set MEMORY_TARGET to at least the recommended value.

In this case the increase of your processes parameter was the root cause of the ORA-00838 error. As we my know the processes parameter determines the sessions parameter that this must, in turn, indicate to Oracle that additional RAM is required to support the extra sessions.
As a workaround, of course, you can increase your memory_target parameter value.

ora-12560: TNS Protocol adapter error Troubleshooting

ORA-12560 error