ORA-12519, TNS:no appropriate service handler found

Caused by: oracle.net.ns.NetException: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found  

SQL> set lines 200

SQL> select * from v$resource_limit where resource_name = 'processes';

RESOURCE_NAME                  CURRENT_UTILIZATION MAX_UTILIZATION INITIAL_ALLOCATION                       LIMIT_VALUE                                  CON_ID

------------------------------ ------------------- --------------- ---------------------------------------- ---------------------------------------- ----------

processes                                      988            1000       1000                                     1000                                        0

SQL> select count(1) FROM v$session;

  COUNT(1)

----------

       969

SQL> select status,count(1) FROM v$session group by status;

STATUS     COUNT(1)

-------- ----------

ACTIVE           46

INACTIVE        923

We have seen lots if INACTIVE sessions which we need to kill.  After killing sessions that were INACTIVE for a very long time. We don't see the errors anymore after re-executing the deployment.

SQL> select status,count(1) FROM v$session group by status;

STATUS     COUNT(1)

-------- ----------

ACTIVE           46

INACTIVE        310

SQL> select count(1) FROM v$session;

  COUNT(1)

----------

       356

SQL>

Vagrant was unable to mount VirtualBox shared folders

I got this error below while starting vagrant. I am dependent on using CLI in  my work so i need to find a solution. 

C:\>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/centos-7.3' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: No guest additions were detected on the base box for this VM! Gues

    default: additions are required for forwarded ports, shared folders, host o
ly
    default: networking, and more. If SSH fails on this machine, please install
    default: the guest additions and repackage the box to continue.
    default:
    default: This is not an error message; everything may continue to work prop
rly,
    default: in which case you may ignore this message.
==> default: Mounting shared folders...
    default: /vagrant => C:/
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device


Found some discussions in the stackoverflow. And i tried 1 solution below.


C:\>vagrant plugin install vagrant-vbguest
Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
Fetching: vagrant-share-1.1.9.gem (100%)
Fetching: micromachine-2.0.0.gem (100%)
Fetching: vagrant-vbguest-0.15.1.gem (100%)
Installed the plugin 'vagrant-vbguest (0.15.1)'!

I tried to reinstall it again since i forgot to shut it down first before i install the vagrant-vbgust plugin. 

C:\>vagrant halt
==> default: Attempting graceful shutdown of VM...

Since i was already installed in the first run it does not do anything.

C:\>vagrant plugin install vagrant-vbguest
Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
Installed the plugin 'vagrant-vbguest (0.15.1)'!

Then i started the vagrant. After starting it the vagrant reinstalled some libraries.

C:\>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/centos-7.3' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
==> default: Machine booted and ready!
[default] No installation found.
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: ftp.tsukuba.wide.ad.jp
 * extras: ftp.tsukuba.wide.ad.jp
 * updates: ftp.tsukuba.wide.ad.jp
Package binutils-2.25.1-32.base.el7_4.1.x86_64 already installed and latest vers
ion
Package 1:make-3.82-23.el7.x86_64 already installed and latest version
Package 4:perl-5.16.3-292.el7.x86_64 already installed and latest version
Package bzip2-1.0.6-13.el7.x86_64 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package gcc.x86_64 0:4.8.5-16.el7_4.1 will be installed
--> Processing Dependency: cpp = 4.8.5-16.el7_4.1 for package: gcc-4.8.5-16.el7_
4.1.x86_64
--> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.8.5-16.el
7_4.1.x86_64
---> Package kernel-devel.x86_64 0:3.10.0-693.11.6.el7 will be installed
--> Running transaction check
---> Package cpp.x86_64 0:4.8.5-16.el7_4.1 will be installed
---> Package glibc-devel.x86_64 0:2.17-196.el7_4.2 will be installed
--> Processing Dependency: glibc-headers = 2.17-196.el7_4.2 for package: glibc-d
evel-2.17-196.el7_4.2.x86_64
--> Processing Dependency: glibc-headers for package: glibc-devel-2.17-196.el7_4
.2.x86_64
--> Running transaction check
---> Package glibc-headers.x86_64 0:2.17-196.el7_4.2 will be installed
--> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.
17-196.el7_4.2.x86_64
--> Processing Dependency: kernel-headers for package: glibc-headers-2.17-196.el
7_4.2.x86_64
--> Running transaction check
---> Package kernel-headers.x86_64 0:3.10.0-693.11.6.el7 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
 Package             Arch        Version                     Repository    Size
================================================================================
Installing:
 gcc                 x86_64      4.8.5-16.el7_4.1            updates       16 M
 kernel-devel        x86_64      3.10.0-693.11.6.el7         updates       14 M
Installing for dependencies:
 cpp                 x86_64      4.8.5-16.el7_4.1            updates      5.9 M
 glibc-devel         x86_64      2.17-196.el7_4.2            updates      1.1 M
 glibc-headers       x86_64      2.17-196.el7_4.2            updates      676 k
 kernel-headers      x86_64      3.10.0-693.11.6.el7         updates      6.0 M
Transaction Summary
================================================================================
Install  2 Packages (+4 Dependent packages)
Total download size: 44 M
Installed size: 95 M
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
--------------------------------------------------------------------------------
Total                                              2.8 MB/s |  44 MB  00:15
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : kernel-headers-3.10.0-693.11.6.el7.x86_64                    1/6
  Installing : glibc-headers-2.17-196.el7_4.2.x86_64                        2/6
  Installing : glibc-devel-2.17-196.el7_4.2.x86_64                          3/6
  Installing : cpp-4.8.5-16.el7_4.1.x86_64                                  4/6
  Installing : gcc-4.8.5-16.el7_4.1.x86_64                                  5/6
  Installing : kernel-devel-3.10.0-693.11.6.el7.x86_64                      6/6
  Verifying  : cpp-4.8.5-16.el7_4.1.x86_64                                  1/6
  Verifying  : glibc-devel-2.17-196.el7_4.2.x86_64                          2/6
  Verifying  : kernel-devel-3.10.0-693.11.6.el7.x86_64                      3/6
  Verifying  : glibc-headers-2.17-196.el7_4.2.x86_64                        4/6
  Verifying  : gcc-4.8.5-16.el7_4.1.x86_64                                  5/6
  Verifying  : kernel-headers-3.10.0-693.11.6.el7.x86_64                    6/6

Installed:
  gcc.x86_64 0:4.8.5-16.el7_4.1    kernel-devel.x86_64 0:3.10.0-693.11.6.el7
Dependency Installed:
  cpp.x86_64 0:4.8.5-16.el7_4.1
  glibc-devel.x86_64 0:2.17-196.el7_4.2
  glibc-headers.x86_64 0:2.17-196.el7_4.2
  kernel-headers.x86_64 0:3.10.0-693.11.6.el7

Complete!
Copy iso file C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso into the
 box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: /dev/loop0 is write-protected, mounting read-only
Installing Virtualbox Guest Additions 5.1.28 - guest version is unknown
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.1.28 Guest Additions for Linux...........
VirtualBox Guest Additions installer
Removing installed version 5.1.26 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
vboxadd.sh: Starting the VirtualBox Guest Additions.
Could not find the X.Org or XFree86 Window System, skipping.
Redirecting to /bin/systemctl start vboxadd.service
Redirecting to /bin/systemctl start vboxadd-service.service
Unmounting Virtualbox Guest Additions ISO from: /mnt
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
    default: /vagrant => C:/
==> default: Machine already provisioned. Run `vagrant provision` or use the `--
provision`
==> default: flag to force provisioning. Provisioners marked to run always will
still run.

After everything was done tried to access vagrant via PUTTY and now the my local drive is now accessible via vagrant. How cool is that!!!!! 

Just another issue while browsing my local directory via vagrant. I throws an error while browsing some Windows default directory. I am not sure why but the important thing is i am able to access my Work directory.

[root@localhost vagrant]# ls -ltr

ls: cannot read symbolic link Documents and Settings: Protocol error

total 14211895

-rwxrwxrwx. 1 vagrant vagrant       5686 Nov  7  2007 vcredist.bmp

.