I have installed oracle 11g, but got this error: "ORA-12705: Cannot access NLS data files or invalid environment specified" while I was trying to connect to it from eclipse. I googled alot and finally changed my nls language and territory settings + my windows language and territory settings (from Russian to English(American)). But that didnt solve the problem, so I decided to reinstall the oracle 11g. And got myself a step back in solving the problem by generating another error even before the first error. I tried to manualy set the environmental variable ORACLE_HOME, didnt help. Also I tried to login to the sqlplus as "sysdba" and then to launch the "startup" command. This brought me an error that my "spfilexe.ora" is missing, so maybe that could be the problem. And I have started the oracle database before. I would appreciate any suggestions on how to solve this problem.
Related
I got the error on the title in my project (which is working well in production on remote server). My local server is Apache, WAMP package.
By default, SQL Server is the database conection so I can't even login. I'm going to share many screenshots because I try many solutions what I found while searching on Google but no one fix my issue.
First of all, the exception message which is almost the same for everyone.
[
So now, my System variables with PHP and Postgrade path.
Here is the PHP Extension list enabled/disabled
And the "extension_dir" on PHP.ini
Finally, laravel files setting up the connection...
start.php -> set my "local" environment
and my local/database.php settings
So I got eveything properly setted (I think) and even like this I can't connect.
Any some other help, please?
Finally, the problem was the arquitecture used on WAMP, should be 32bits, not 64 as I got.
I'm working on a Mavericks machine running a Windows 8.1 VM, trying to install an Oracle Database 12c. The installation runs fine up until it gets to the Database Configuration Assistant portion, where it immediately gives me the error mentioned above, "ORA-12560: TNS:protocol adapter error".
The database installer gives the option to skip a step, so I've tried doing so, and the database installation continues and completes. After it is completed, the Database Configuration Assistant is installed as an application. Running this application gives the same error immediately after setting some of the basic information (like database name, password, etc.).
I'm more or less brand new to Oracle databases, and I have no clue as to what this error might mean, or how to fix it. Does anybody have any idea as to why this error is appearing? I'm eager to provide any more information if it's needed, and would greatly appreciate any ideas or tips.
Thanks!
It seems to me that your oracle database is not up and running, this is a common issue for some first time users, what you need is to setup your database before anything else.
Try going to Control Panel, then Administrative Tools, then Services. Restart both OracleXETNSListener and the OracleServiceXE.
Or just go to start Start >> Run >> type "services.msc"
search for OracleXETNSListener and OracleServiceXE, right click then hit Start.
I encountered a rather strange error earlier while deploying an SSIS project to our SSIS Catalogue DB:
"The project or operation records do not exist or you have not been
granted the appropriate permissions to view them."
Now, I'm an administrator on the server and have never had any trouble deploying to it before. I tried again just afterwards, and it worked fine. I checked to make sure that there were no other packages running at the same time.
I did find this recent post on MSDN, which has the same error but no explanation as of yet.
Anybody know what the cause of this error could be?
try open solution "Run as Administrator" it can help.
Perhaps your project did not exist at the time of the deployment but was created so the next time you deployed you did not get the error because it actually passed that validation. Double Check the deployment information, the name and path of the deployment destination and confirm that those existed.
I am stuck with something really nasty here. I have a SSAS Cube that was working fine till day before yesterday. Had some performance issues on the server and got cummulative patch 938077 on top of Service Pack2.
Since then I have not been able to deploy the cube - with a strange error -
File System Error: The following error occurred during a file operation: Access is denied.
I am administrator on the machine, have possibly checked the whole of file system for permissions. Have deleted the existing cube, stopped services, server, tried redeployment - nothing works.
Unfortunately I forgot to take a snapshot of pre-patch image, so cann't restore back. Only option I am currently left with is to rebuild the server, if I cann't fix this.
Strange but I cann't find anything on any forums about this.
Yes, one more strange thing related to this - I had SSIS package, to load DW (datasource for above cube), and strangely I have lost all my Data flow tasks. Something wierd is really going on and I cann't trace it.
Any suggestions or help would be great. I just cann't think of anything right now.
Cheers!!
Vineet
Figured it out, its more of a permission issue on the server than with the cube itself. Ran the SQL services under Local System account (after new security patches applied without us knowing it) and it worked fine.
I'm getting an error whenever I load Management Studio or open a folder in the server explorer, etc. Additionally, If I try to create a new database it constantly is updating and does not finish. I have attached a screenshot of the error. Please let me know what I can do to fix this because it's really aggravating.
Error Screen http://frickinsweet.com/databaseError.gif
From MSDN forum http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=120476&SiteID=1
My first guess would be Client Tool corruption.
I've occasionally had to uninstall my client tools and reinstall them. Boot after uninstall.
I had to add the registry file AND re-run "regsvr32 actxprxy.dll" This was a really odd and painful error. It only seemed to come into existence after installing VS SP1 but I really don't see why that would have happened.