SQL Plus with error error checking directory existence during ADR initialization but directory exists - sqlplus

I'm new to Oracle. I have installed it and I'm trying to Create a user in SQL plus. I used the following instructions:
-- 1. In The SQL Plus command prompt, enter user-name as sqlplus / as sysdba.
-- 2. Press Enter.
-- 3. In the Enter Password prompt, press Enter to log in without a password.
-- Note: The Connected to 19c database: message appears.
But then I restarted my computer because I was at the same time installing another software.
After that, trying to continue with SQL plus, I did the same procedure and got the following message: Connected to an idle instance. Instead to Connected to 19c database.
Then I read that shouting down the database and starting it up again would work. And I shouted it down but then when I tried to start it up I got this error:
--SQL> startup
--ORA-48173: error checking directory existence during ADR initialization
--[C:\app\client\ivoespin\diag\rdbms\orcl]
--ORA-48187: specified directory does not exist
--OSD-00002: additional error information
--O/S-Error: (OS 5) Access is denied.
But I checked and the directory exists with an orcl folder and a i_1.mif file in it.
What am I missing?

Related

read unix #->/var/run/docker.sock: read: connection reset by peer

I'm populating blockchains database with my backup script backup_2019-05-21.sql, but running this command on CLI shows this error.
some_user#my_project:~$ docker exec -i mysql_test mysql -uroot -ptestpass blockchains < /home/some_user/db_backups/backup_2019-05-21.sql
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'mysqldump: [Warning] Using a password on the command line interface can be insec' at line 1
read unix #->/var/run/docker.sock: read: connection reset by peer
Note: backup_2019-05-21.sql file size is 5G
Someone know the exact reason ? :)
The first line of your backup:
[Warning] Using a password on the command line interface can be insecure.
Is not valid sql. It appears to be an error log interspersed with your sql dump. If you can run your backup again, you'll want to do so without capturing these error messages. If that's not possible, you'll need to remove these logs from your sql file before trying to import it.

How to take dump of neo4j graph databases?

I had my all databases stored at a location C:\JATIN DATA\database\neo4jDatabases. How can I take the dump of all databases individually using neo4j Dekstop.
I had already tried neo4j-admin dump --database= --to= this command but getting errors like Neo.ClientError.Statement.SyntaxError: Invalid input 'n': expected (line 1, column 1 (offset: 0))
"neo4j-admin dump --database= --to="
^
neo4j-admin must be run from a terminal command line -- not from the neo4j Browser.
Since you are using the Desktop, you can open a terminal window to the appropriate directory by selecting your neo4j Project from the Projects panel on the left, click the Manage button of the database you want to dump, And then select the Terminal tab.
Once in the Terminal window, you can enter a command like the one suggested by #logisma:
bin/neo4j-admin dump --database=graph.db --to=c:\
Thanks #cybersam and #logisima finally dump is taken successfully. This is the complete command .\bin\neo4j-admin.bat dump --database=graph.db --to=c:\dump\article_citation_graph.dump there was some admin privilege error.
Have you try this : .\bin\neo4j-admin.bat dump --database=graph.db --to=c:\
This should create a file named graph.db.dump in your c:\ folder.

Ruby on Rails project with Postgres DB, created on Macbook, need to access on windows 10

A while ago I created a Ruby on Rails project with a postgres database. It was originally created on a macbook where I had set up a working production and test environment. Unfortunately, this computer has died and now I have to continue working on the same project using the only machine I have: a Windows 10 laptop.
I have been following these guides to set up a viable rails environment on my windows 10 pc:
https://medium.com/#colinrubbert/installing-ruby-on-rails-in-windows-10-w-bash-postgresql-e48e55954fbf
https://gorails.com/setup/windows/10
I have installed bash/ubuntu successfully. I have installed git successfully. I have installed ruby successfully. I have installed all the pre-requisite gems so that I can run bundle install successfully. When I get to postgres, as suggested by both tutorials, I install it via windows instead of installing it by terminal. With Postgres 9.6 installed and running as a windows service, I'm unable to enter psql in the terminal. I get this error:
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
Additionally, here are the errors that appear when I attempt to do something with rake db commands:
FATAL: role "xxx" does not exist
Couldn't create database for {"adapter"=>"postgresql", "encoding"=>"unicode", "pool"=>5, "database"=>"YelpClone_development", "host"=>"localhost"}
rake aborted!
ActiveRecord::NoDatabaseError: FATAL: role "xxx" does not exist
'xxx' above is my username. I'm not sure if its the username from my old mac or on my new windows machine. I've attempted to edit the database.yml inside my rails project but that gets the same results.
Looking at this topic about the role error, I attempted to use the command "sudo -u postgres -i" which results in another error:
sudo: setresuid() [1000, 112, 1000] -> [-1, 0, -1]: Operation not permitted
sudo: unable to set runas group vector: Operation not permitted
sudo: unable to mkdir /var/run/sudo: Permission denied
[sudo] password for xxx:
sudo: PERM_ROOT: setresuid(0, -1, 0): Operation not permitted
xxx is not in the sudoers file. This incident will be reported.
Once again 'xxx' is my username. Now I'm beginning to suspect that all this stuff did NOT install correctly. But I'm unsure how I can check. I've tried re-installing postgres about 5-6 times now. Can anyone shed some light on this mess?
I have found a solution to this problem and I thought I would post how I solved it in case anyone else had the same issues:
I followed the instructions found on this page for issues specific to the WSL (Windows subsystem for Linux), specifically posted by user leafofLegend.
The main problem I had was getting stuck on step 7. I had to downgrade my postgres install to 9.3 in order to have PGAdmin 3 instead of 4 as it no longer has editing features for server config. The 2nd issue was being unable to access the ~/.bashrc file. I attempted to open it in atom (via terminal) but it would show me a blank file each time. Alternatively, if I navigated to the file on windows and opened it there, it would become corrupted and not source to the terminal properly. You CANNOT edit linux files using windows tools. Therefore I had to use nano editor to edit the ~./bashrc file as stated in step 9.
The above steps solved the bulk of the problem, which was getting a windows installed PG to be friendly with a WSL terminal. Following the rest of the steps, I'm now able to run rake DB commands and create new dbs.

'SQL1024N A database connection does not exist. SQLSTATE=08003' error while executing 'db2 -x' command through command stage in Datastage 9.1

I'm getting 'SQL1024N A database connection does not exist. SQLSTATE=08003' error, while executing 'db2 -x' command through execute command stage in Datastage 9.1(AIX Server). Can any one please help me out ?
To connect to DB2 - you need a catalog entry on your Linux server ( or wherever the Datastage in installed)
You may need to check with the datastage administrator.
Use the below command on the server to see all the cataloged db2 databases
db2 list db directory
You may need to source the dsenv before you run this.

PSEXEC - Elevated Command prompt

Sorry if this has been asked a hundred times, I'm sure it might have been, but my searching skills don't seem to be finding the answer to my particular question today :(
I'm trying to execute a command on a server, from a domain user account, who has all the correct rights to perform the given action. I know this because if I login to the server under the admin account and then open the command prompt using 'Run as different User', specifying the login details of the domain user account, I can perform the relevant section of the below command successfully.
However, when I try running ("c:\NaviTest\psexec.exe" "\HOSTNAME" "c:\path to\server-command.exe" "arguments") from a command prompt on their host computer I get the 'Access Denied' message back.
If I launch the command prompt as administrator and change the syntax of the command as follows (where username is the logged in user and password is their password);
"c:\NaviTest\psexec.exe" -u username -p password "\\HOSTNAME" "c:\path to\server-command.exe" "arguments"
All works.
I know from this that its not running 'server-command.exe' the command that is causing the issue, its getting the connection to server using PSEXEC which seems to be failing unless the command prompt is being run in Elevated mode.
My question (as I haven't actually asked on yet!), is can PSEXEC work from the command prompt without having to be run administratively?
I'm trying to execute this as part of a much larger script, if I can't make it work without administrative privileges its not going to work.
Found the answer to this.......
https://serverfault.com/questions/280482/how-to-use-psexec-without-admin-privileges-on-target-machine
Basically, the user account executing the PSEXEC command needs local administrative rights on the destination host.
Adam
This might cause due to prevailing issue.
psexcec will start a service(windows) in end point .
check this
Run this as admin and will proceed without issues

Resources