User login
|
|
|
|
Frontpage Sponsor
|
|
|
|
Poll
|
As a Customer What would do to keep your ERP Implementation intact Proactively define Business Process-- Take the Project Ownership 50% Handover everything to System Integrator from drawing BP till implementation of ERP 17% Hire more inhouse skilled & capable IT Resource to work directly with SI 33% Rely on SI Architects/Consultants 0% Total votes: 12 |
|
Baanboard at LinkedIn
|
|
|
|
 |
24th March 2017, 08:51
|
|
Junior Member
|
|
Join Date: Aug 2014
Posts: 10
|
|
|
Baan: fp7 -
DB: oracle -
OS: windows
|
A new blog entry has been added:
unable to create table
|
24th March 2017, 12:30
|
 |
Guru
|
|
Join Date: Apr 2002
Location: Germany, 50.584097,8.544078
Posts: 1,903
|
|
|
Baan: 2.2/3.1/4c4/LN6.1 FP6/FP9/HiDox Tools 10.7 -
DB: tbase, ms-sql7, oracle10gV1, 11g, 12c, 19c -
OS: HP-UX, W2K3, SLES, RHLE
|
|
leave after CRDD an login again !!!!!!!
Hello,
after maintaining a new table Definition and CRDD you have to leave the application an log in again.
After NEW Login the create table should be successful.
Post in proper Forum , please.
NO BLOG !
Regards
__________________
//Bernd
|
31st March 2017, 08:49
|
 |
Guru
|
|
Join Date: Jan 2002
Posts: 584
|
|
|
Baan: Baan IV, Baan 5.0c, Infor LN -
DB: Oracle, Sql Server, PostgreSQL -
OS: Unix, Linux, Windows
|
|
I saw that you have this error: "Error 510 - Database not on" and "Cannot open new ODBC connection for session".
Probably, there is something wrong with database group on DB level - changed password or missing authorization.
|
3rd February 2021, 19:37
|
|
Newbie
|
|
Join Date: Jun 2017
Posts: 1
|
|
|
Baan: Baan 4 C4 -
DB: Oracle -
OS: Linux
|
|
We are facing exactly same error in 10.5 .
How did you resolve this error? Please suggest.
|
4th February 2021, 17:32
|
 |
Guru
|
|
Join Date: Mar 2002
Location: Frederick, CO
Posts: 458
|
|
|
Baan: Baan IVc3, IVc4, 5b, 5c, ERP LN 6.1, Infor ERP 10.x -
DB: SQL Server, Oracle -
OS: Windows, Linux, HPUX, AIX, (a little bit of) Solaris
|
|
Sounds like the database login that corresponds to the database group doesn't have permissions to execute DDL statements. For SQL Server, anyway, if your LN database group is "lndb", there should be a SQL login named "lndb", and the database name for LN should be "lndb". The SQL login "lndb" should either be the db_owner for lndb or have a corresponding lndb database user that has the db_owner role.
__________________
Vincent Murphy
---------------
ERP Practice Manager / Senior Consultant
OST
vmurphy@ostusa.com
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
|
|
|
| Thread Tools |
|
|
| Display Modes |
 Linear Mode
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
