Hello all,
I'm attempting to import into 9.2.0.1.0 from 7.3.4 and I'm getting loads of
the same error:
IMP-00017: following statement failed with ORACLE error 9275:
GRANT SELECT ON DOWNLOAD_SEQ TO INTERNAL
IMP-3: ORACLE error 9275 encountered
ORA-09275: CONNECT INTERNAL is not a valid DBA
Barry,
Why make life difficult? It's just a role, not a data
object referenced by applications (hopefully). Change it's
name to something that is not a reserved word and move on.
There is a list of reserved words in the SQL Language
reference.
Hope this helps...
-Tim
Hello all,
I'm
Tim,
I checked v$reserved_words. At least in 9.2.0.1, INTERNAL is not in there.
Oracle should address this issue.
When I trace the SQL GRANT SELECT ON SOMETABLE TO INTERNAL, it stops in
parsing.
Nonetheless, it's confusing to say the least to create a role called internal.
Yong Huang
--- Tim
Oops! blush Thanks for the correction, Yong!
Tim,
I checked v$reserved_words. At least in 9.2.0.1, INTERNAL
is not in there. Oracle should address this issue.
When I trace the SQL GRANT SELECT ON SOMETABLE TO
INTERNAL, it stops in parsing.
Nonetheless, it's confusing to say the
Yong,
It seems to me that you are missing the point here. The real point is that
you should not have granted select on some table to internal - ever. And
a new release caught you on this mistake. And now, you have to fix it. It
is not an Oracle problem, but a mis-use of an Oracle internal
As of yet I'm unsure how the application would be affected if I rename the
role - I need to do some investigation.
I tried this in Oracle 8 and it worked fine - It just seems to be oracle 9
that doesn't like it.
I've also checked v$reserved_words and INTERNAL is not listed, INTERNAL_USE
and
This would explain why it worked when I tried it on oracle 8 then.
The developers that originally created the application left quite a while
ago, so I don't think I'll be able to ask them why they did it this way.
But basically you're saying that it shouldn't have been done like this and
now it
sounds hardcoded in the kernel about the internal user, reserved word or
not, its just a bad idea.
joe
Barry Deevey wrote:
As of yet I'm unsure how the application would be affected if I rename the
role - I need to do some investigation.
I tried this in Oracle 8 and it worked fine - It just
Barry,
What you need to do is stop using the INTERNAL role.
Create your own role. Grant access to the tables to this role. And then
grant this role to your application user. Everything should be fine.
As I said, you made a mistake back when you started using the INTERNAL role.
Now that
INTERNAL_USE is an keyword (to enable an undocumented feature) in ALTER
DATABASE
command. THis can be used to convert the database character set if the
existing
char set (national charset) is the superset of the db charset. You can just
run
the ALTER Database command to convert the db charset.
Yong didn't do it, he merely posted a reply.
Mercadante, Thomas F [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
11/18/2003 06:54 AM
Please respond to ORACLE-L
To:Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:RE: 'internal' role and 9i
Yeah,
I realized that afterward - sorry Yong.
Tom Mercadante Oracle Certified Professional
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Sent: Tuesday, November 18, 2003
11:24 AMTo: Multiple recipients of list ORACLE-LSubject:
RE: 'internal' role and
Gopal,
Are you saying with an undocumented parameter or command, I can alter database
(national) character set us7ascii even if my current (national) character set
is utf8?
Yong Huang
--- K Gopalakrishnan [EMAIL PROTECTED] wrote:
INTERNAL_USE is an keyword (to enable an undocumented feature)
Yong,
You said It's not always easy to have a futuristic view to avoid potential
problems. The
developer probably shouldn't have granted anything to internal back then.
But
it wasn't obvious at that time that doing so could cause a problem later.
I totally disagree with you. Your quote implies
Barry,
I suggest you open a Tar with Oracle, unless you're sure changing your
application is easy. Oracle obviously missed this little detail by
over-rejecting a previously legitimate role. If 9i's Release note doesn't say
how to deal with this case, then Oracle support should open a bug.
Tom,
INSERT STANDARD DISCLAIMERS
Yes. You can use INTERNAL_USE keyword to convert the database character set.
I think there is a utility called 'csscan' character set scanner which can
be
used to determine the possibility of the INTERNAL_USE conversion.
END DISCLAIMERS
Best Regards,
K
Gopal,
In case I didn't make my message clear, I wanted to know if using that keyword
allows us to change character set from a superset to a subset (e.g. from UTF8
to US7ASCII). The documented command ALTER DATABASE CHARACTER SET new charset
is only for changing from a subset to a superset. If
by: Subject: RE: alter database character
set (Was: RE: 'internal' role and 9i)
ml-errors
I've never used that, but this syntax seems to work:
alter database character set internal_use us7ascii;
Of course, you could lose some characters or mess up your data completely
that way...
Tanel.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent:
19 matches
Mail list logo
