After upgrading to 3.1.2 from 3.1.1, I get the following error when retrieving the login page:
Backend ERROR: OTRS-CGI-10 Perl: 5.8.8 OS: linux Time: Thu Mar 22 13:49:38 2012 Message: ERROR OCIEnvNlsCreate. Check ORACLE_HOME (Linux) env var or PATH (Windows) and or NLS settings, permissions, etc. Traceback (19221): Module: Kernel::System::DB::new (v1.144) Line: 227 Module: Kernel::System::Web::InterfaceAgent::Run (v1.64) Line: 143 Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 46 Module: (eval) (v1.90) Line: 204 Module: ModPerl::RegistryCooker::run (v1.90) Line: 204 Module: ModPerl::RegistryCooker::default_handler (v1.90) Line: 170 Module: ModPerl::Registry::handler (v1.99) Line: 31
I am running Centos 5.7. 3.1.1 was working fine.
Also, otrs.CheckDB.pl says the database connection looks OK.
Any thoughts?
Thanks
Richard
OCIEnvNlsCreate error after upgrade from 3.1.1 to 3.1.2
Moderator: crythias
-
- Znuny newbie
- Posts: 7
- Joined: 22 Mar 2012, 20:57
- Znuny Version: OTRS313
- Real Name: Ricahrd Mertz
- Company: City of Evanston
-
- Znuny newbie
- Posts: 7
- Joined: 22 Mar 2012, 20:57
- Znuny Version: OTRS313
- Real Name: Ricahrd Mertz
- Company: City of Evanston
Re: OCIEnvNlsCreate error after upgrade from 3.1.1 to 3.1.2
I found the problem. The documentation says to do a "service httpd start". If I do that, I get the error. If I run the init.d/httpd script to start it, it works fine.
Richard
Richard
Richard Mertz
OTRS 3.1.5
Oracle 11g
Centos 5.6
OTRS 3.1.5
Oracle 11g
Centos 5.6
Re: OCIEnvNlsCreate error after upgrade from 3.1.1 to 3.1.2
if you put the Oracle Environment Variables in the init script thats correct
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny newbie
- Posts: 2
- Joined: 09 Jul 2012, 10:27
- Znuny Version: 3.1.7
- Real Name: Dariusz Kryszak
- Company: Cloudware Polsak Sp. z o.o.
Re: OCIEnvNlsCreate error after upgrade from 3.1.1 to 3.1.2
I've made upgrade of my OTRS version from 3.1.2 to 3.1.7.
After that my helpdesk worked fine. Today, I've tried to login and without success.
When I want to open default page I've got error occured:
ERROR OCIEnvNlsCreate. Check ORACLE_HOME (Linux) env var or PATH (Windows) and [..]
Jojo said that add ora env to script is enought. But which one? Which one script shoud I change?
Thanks for any suggestions.
Additionaly when I'm trying start otrs-scheduler-linux occured:
service otrs-scheduler-linux start
Starting OTRS SchedulerDBD::Oracle::db disconnect failed: ORA-03113: koniec pliku w kanale komunikacyjnym
ID procesu: 0
ID sesji: 43, numer seryjny: 191 (DBD ERROR: OCISessionEnd) at /opt/otrs/Kernel/System/DB.pm line 301.
After that my helpdesk worked fine. Today, I've tried to login and without success.
When I want to open default page I've got error occured:
ERROR OCIEnvNlsCreate. Check ORACLE_HOME (Linux) env var or PATH (Windows) and [..]
Jojo said that add ora env to script is enought. But which one? Which one script shoud I change?
Thanks for any suggestions.
Additionaly when I'm trying start otrs-scheduler-linux occured:
service otrs-scheduler-linux start
Starting OTRS SchedulerDBD::Oracle::db disconnect failed: ORA-03113: koniec pliku w kanale komunikacyjnym
ID procesu: 0
ID sesji: 43, numer seryjny: 191 (DBD ERROR: OCISessionEnd) at /opt/otrs/Kernel/System/DB.pm line 301.
-
- Znuny newbie
- Posts: 2
- Joined: 09 Jul 2012, 10:27
- Znuny Version: 3.1.7
- Real Name: Dariusz Kryszak
- Company: Cloudware Polsak Sp. z o.o.
Re: OCIEnvNlsCreate error after upgrade from 3.1.1 to 3.1.2
Solution.
Check of the httpd/conf.d/ files:
otrs.conf
zzz_otrs.conf
zzz_otrs.conf.org
zzz_otrs.conf and otrs are duplication of configuration.
After rename file zzz_otrs.conf to zzz_otrs.conf.blabla
everything started working fine.
Check of the httpd/conf.d/ files:
otrs.conf
zzz_otrs.conf
zzz_otrs.conf.org
zzz_otrs.conf and otrs are duplication of configuration.
After rename file zzz_otrs.conf to zzz_otrs.conf.blabla
everything started working fine.