I’ve been fine-tuning my SQL Developer Tips presentation, having given it at RMOUG and now electronically for ODTUG. Still a lot of work to do until it is ‘perfect,’ but folks already seem to enjoy it (if not me.)
What I have left to do is trim the fat so I can shove as many tips and tricks into an hour presentation!
If you want to review the slides, here they are:
Of course I recommend you go straight to the source, which would be all of the ‘SQL Developer’ category posts on this blog. If you want a shortcut to the best posts, then use the SQL Developer resource page I put together.
Do you have a favorite tip or trick that I’m missing? Please share it here in the form of a comment. I’ll try to work it in for the ‘next release.’
You can see this ‘live’ and in-person for the following events:
- Central Florida Oracle User Group (CFOUG), May 23
- SUNCOAST Oracle User Group Meeting (SOUG), May 24
- ODTUG Kscope12 Monday June 25, Session 5, 4:15 pm – 5:15 pm
- A really, really big show in San Francisco this Fall
Would you like me to present to your company or organization?
Just ask!
Twitter
RSS
GooglePlus
Facebook
Aug 22, 2012 @ 16:35:42
I’ve seen a couple of your webcasts and several people in my department use SQL Developer (versoin 3). It’s a great tool. We’re having an odd problem now, though. In some schemas we cannot copy tables via the right-click on the table, select Table>Copy. One person who’s tried this gets a table not found error. When I try it, nothing happens. I had a DBA review the security in the schema that doesn’t work and compare it to one that does work. Nothing jumps out as a potential cause. The user can create tables. Do you have any idea what the problem might be?
Thanks.
Jerry
Aug 22, 2012 @ 16:39:51
What happens if you take the generated script from the SQL panel on the pop-up and run that in the Worksheet or SQL*Plus?
Appreciate your support and hanging out at our webcasts. And thanks for reaching out with your issue. I’ll do my best to get it going for you!
One note, you’re now 2 versions behind (3.1, 3.2) – we might be looking at a bug that’s been fixed since v3.0.
Aug 22, 2012 @ 17:26:01
Figured it out. It turns out it was a security issue. In order to copy a table in SQL Developer the user needs access to the ALL_USERS view. That was revoked from everyone this past year as part of security vulnerability remediation. Someone else ran into this, though, since the DBAs created a special role just for this. Once the user was granted the role, it worked.